Vehicle Wireless Device Discovery

ABSTRACT

A first V2X wireless device may transmit a first discovery request to a V2X network entity. The a V2X network entity may comprise a first wireless device identifier and a V2X value. The V2X value may indicate a V2X communication capability. The first V2X wireless device may receive a first discovery response from the V2X network entity. The first discovery response may comprise a first discovery code. The first discovery code may correspond to at least the V2X value. The first V2X wireless device may perform a discovery procedure. The discovery procedure may employ the first discovery code. The first V2X wireless device may communicate, with a second V2X wireless device by employing the V2X communication capability, one or more packets in response to the discovery procedure connecting the first V2X wireless device with the second V2X wireless device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/732,540, filed Jan. 2, 2020, which is a continuation of U.S.application Ser. No. 15/469,023, filed Mar. 24, 2017 and now U.S. Pat.No. 10,582,443, which claims the benefit of U.S. Provisional ApplicationNo. 62/313,171, filed Mar. 25, 2016, and of U.S. Provisional ApplicationNo. 62/313,174, filed Mar. 25, 2016, which are hereby incorporated byreference in their entirety for all purposes.

BRIEF DESCRIPTION OF THE DRAWINGS

Examples of several of the various embodiments of the present inventionare described herein with reference to the drawings.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per anaspect of an embodiment of the present invention.

FIG. 2 is a diagram depicting an example transmission time and receptiontime for two carriers in a carrier group as per an aspect of anembodiment of the present invention.

FIG. 3 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present invention.

FIG. 4 is a block diagram of a base station and a wireless device as peran aspect of an embodiment of the present invention.

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present invention.

FIG. 6 is an illustration of an example one to one V2X communication asper an aspect of an embodiment of the present disclosure.

FIG. 7 is an illustration of an example one to many V2X communication asper an aspect of an embodiment of the present disclosure.

FIG. 8A and FIG. 8B illustrate example V2P communications as per anaspect of an embodiment of the present disclosure.

FIG. 9A and FIG. 9B illustrate example V2P communications through anetwork as per an aspect of an embodiment of the present disclosure.

FIG. 10A and FIG. 10B illustrate example V2I communications as per anaspect of an embodiment of the present disclosure.

FIG. 11A and FIG. 11B illustrate example V2V communication through anRSU and a network as per an aspect of an embodiment of the presentdisclosure.

FIG. 12A and FIG. 12B illustrate example V2V communication through anRSU as per an aspect of an embodiment of the present disclosure.

FIG. 13A and FIG. 13B illustrate example V2I/P communication through anRSU as per an aspect of an embodiment of the present disclosure.

FIG. 14 is a block diagram of a V2X architecture as per an aspect of anembodiment of the present disclosure.

FIG. 15 is a flow diagram of an example IMS registration of a V2X UE asper an aspect of an embodiment of the present disclosure.

FIG. 16 is a flow diagram of an example IMS registration of a V2X UE asper an aspect of an embodiment of the present disclosure.

FIG. 17 is an example flow diagram showing a V2X UE sending a request toa V2X AS as per an aspect of an embodiment of the present disclosure.

FIG. 18 is an example flow diagram showing a V2X UE sending a request toa V2X AS as per an aspect of an embodiment of the present disclosure.

FIG. 18 is an example flow diagram showing a V2X UE sending a request toa V2X AS as per an aspect of an embodiment of the present disclosure.

FIG. 19 is a block diagram of a V2X broadcast multicast architecture asper an aspect of an embodiment of the present disclosure.

FIG. 20 is a flow diagram showing an example process of a V2X AS sendinginformation about a broadcast/multicast bearer to a V2X UE as per anaspect of an embodiment of the present disclosure.

FIG. 21 is a flow diagram showing an example process of a V2X AS sendinginformation about a broadcast/multicast bearer to a V2X AS as per anaspect of an embodiment of the present disclosure.

FIG. 22 is a diagram showing an example V2X discovery message as per anaspect of an embodiment of the present disclosure.

FIG. 23 is a flow diagram showing an example process for Model ADiscovery as per an aspect of an embodiment of the present disclosure.

FIG. 24 is a flow diagram showing an example process for announcing aV2X UE as per an aspect of an embodiment of the present disclosure.

FIG. 25 is a flow diagram showing an example process for monitoring aV2X UE as per an aspect of an embodiment of the present disclosure.

FIG. 26 is a flow diagram showing an example match report process as peran aspect of an embodiment of the present disclosure.

FIG. 27 is a flow diagram showing an example process for Model BDiscovery as per an aspect of an embodiment of the present disclosure.

FIG. 28 is a flow diagram showing an example discoveree V2X UE processas per an aspect of an embodiment of the present disclosure.

FIG. 29 is a flow diagram showing an example discoverer V2X UE processas per an aspect of an embodiment of the present disclosure.

FIG. 30 is a flow diagram showing an example match report process as peran aspect of an embodiment of the present disclosure.

FIG. 31 is a diagram of an example visibility configuration as per anaspect of an embodiment of the present disclosure.

FIG. 32 is an illustration of an example visibility matrix as per anaspect of an embodiment of the present disclosure.

FIG. 33 is a diagram of an example visibility configuration as per anaspect of an embodiment of the present disclosure.

FIG. 34 is an illustration of an example visibility matrix as per anaspect of an embodiment of the present disclosure.

FIG. 35 is a flow diagram showing a V2X UE distributing media within aV2X group as per an aspect of an embodiment of the present disclosure.

FIG. 36 is a diagram of a visibility matrix illustrating mediadistribution and redistribution as per an aspect of an embodiment of thepresent disclosure.

FIG. 37 is a flow diagram showing a V2X member discovery as per anaspect of an embodiment of the present disclosure.

FIG. 38 is a flow diagram showing an announcement of a neighboring listas per an aspect of an embodiment of the present disclosure.

FIG. 39 is a flow diagram showing the receiving of a Neighboring Listannouncement by a V2X group member as per an aspect of an embodiment ofthe present disclosure.

FIG. 40 is a diagram of an example visibility configuration as per anaspect of an embodiment of the present disclosure.

FIG. 41 is an illustration of an example visibility matrix as per anaspect of an embodiment of the present disclosure.

FIG. 42 is a flow diagram showing a UE generating media for reception byanother UE as per an aspect of an embodiment of the present disclosure.

FIG. 43 is a diagram of a visibility matrix illustrating mediadistribution and redistribution as per an aspect of an embodiment of thepresent disclosure.

FIG. 44 is a diagram illustrating segmentation of a neighbor list as peran aspect of an embodiment of the present disclosure.

FIG. 45 is a diagram illustrating reverse segmentation of a neighborlist as per an aspect of an embodiment of the present disclosure.

FIG. 46 is a diagram illustrating an example information element of auser diagram protocol as per an aspect of an embodiment of the presentdisclosure.

FIG. 47 is a diagram illustrating an example information element as peran aspect of an embodiment of the present disclosure.

FIG. 48 is a diagram illustrating an example packet format as per anaspect of an embodiment of the present disclosure.

FIG. 49 is a diagram illustrating an example information element as peran aspect of an embodiment of the present disclosure.

FIG. 50 is a diagram illustrating an example information element as peran aspect of an embodiment of the present disclosure.

FIG. 51 is a diagram illustrating an example information element as peran aspect of an embodiment of the present disclosure.

FIG. 52 is a diagram illustrating segmentation of a neighbor list as peran aspect of an embodiment of the present disclosure.

FIG. 53 is a diagram illustrating reverse segmentation of a neighborlist as per an aspect of an embodiment of the present disclosure.

FIG. 54 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure.

FIG. 55 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure.

FIG. 56 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure.

FIG. 57 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure.

FIG. 58 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

The following Acronyms are used throughout the present disclosure:

ASIC application-specific integrated circuit

BPSK binary phase shift keying

CA carrier aggregation

CSI channel state information

CDMA code division multiple access

CSS common search space

CPLD complex programmable logic devices

CC component carrier

DL downlink

DCI downlink control information

DC dual connectivity

EPC evolved packet core

E-UTRAN evolved-universal terrestrial radio access network

FPGA field programmable gate arrays

FDD frequency division multiplexing

HDL hardware description languages

HARQ hybrid automatic repeat request

IE information element

LTE long term evolution

MCG master cell group

MeNB master evolved node B

MIB master information block

MAC media access control

MAC media access control

MME mobility management entity

NAS non-access stratum

OFDM orthogonal frequency division multiplexing

PDCP packet data convergence protocol

PDU packet data unit

PHY physical

PDCCH physical downlink control channel

PHICH physical HARQ indicator channel

PUCCH physical uplink control channel

PUSCH physical uplink shared channel

PCell primary cell

PCell primary cell

PCC primary component carrier

PSCell primary secondary cell

pTAG primary timing advance group

QAM quadrature amplitude modulation

QPSK quadrature phase shift keying

RBG Resource Block Groups

RLC radio link control

RRC radio resource control

RA random access

RB resource blocks

SCC secondary component carrier

SCell secondary cell

Scell secondary cells

SCG secondary cell group

SeNB secondary evolved node B

sTAGs secondary timing advance group

SDU service data unit

S-GW serving gateway

SRB signaling radio bearer

SC-OFDM single carrier-OFDM

SFN system frame number

SIB system information block

TAI tracking area identifier

TAT time alignment timer

TDD time division duplexing

TDMA time division multiple access

TA timing advance

TAG timing advance group

TB transport block

UL uplink

UE user equipment

VHDL VHSIC hardware description language

Example embodiments of the invention may be implemented using variousphysical layer modulation and transmission mechanisms. Exampletransmission mechanisms may include, but are not limited to: CDMA, OFDM,TDMA, Wavelet technologies, and/or the like. Hybrid transmissionmechanisms such as TDMA/CDMA, and OFDM/CDMA may also be employed.Various modulation schemes may be applied for signal transmission in thephysical layer. Examples of modulation schemes include, but are notlimited to: phase, amplitude, code, a combination of these, and/or thelike. An example radio transmission method may implement QAM using BPSK,QPSK, 16-QAM, 64-QAM, 256-QAM, and/or the like. Physical radiotransmission may be enhanced by dynamically or semi-dynamically changingthe modulation and coding scheme depending on transmission requirementsand radio conditions.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per anaspect of an embodiment of the present invention. As illustrated in thisexample, arrow(s) in the diagram may depict a subcarrier in amulticarrier OFDM system. The OFDM system may use technology such asOFDM technology, SC-OFDM technology, or the like. For example, arrow 101shows a subcarrier transmitting information symbols. FIG. 1 is forillustration purposes, and a typical multicarrier OFDM system mayinclude more subcarriers in a carrier. For example, the number ofsubcarriers in a carrier may be in the range of 10 to 10,000subcarriers. FIG. 1 shows two guard bands 106 and 107 in a transmissionband. As illustrated in FIG. 1, guard band 106 is between subcarriers103 and subcarriers 104. The example set of subcarriers A 102 includessubcarriers 103 and subcarriers 104. FIG. 1 also illustrates an exampleset of subcarriers B 105. As illustrated, there is no guard band betweenany two subcarriers in the example set of subcarriers B 105. Carriers ina multicarrier OFDM communication system may be contiguous carriers,non-contiguous carriers, or a combination of both contiguous andnon-contiguous carriers.

FIG. 2 is a diagram depicting an example transmission time and receptiontime for two carriers as per an aspect of an embodiment of the presentinvention. A multicarrier OFDM communication system may include one ormore carriers, for example, ranging from 1 to 10 carriers. Carrier A 204and carrier B 205 may have the same or different timing structures.Although FIG. 2 shows two synchronized carriers, carrier A 204 andcarrier B 205 may or may not be synchronized with each other. Differentradio frame structures may be supported for FDD and TDD duplexmechanisms. FIG. 2 shows an example FDD frame timing. Downlink anduplink transmissions may be organized into radio frames 201. In thisexample, radio frame duration is 10 msec. Other frame durations, forexample, in the range of 1 to 100 msec may also be supported. In thisexample, each 10 ms radio frame 201 may be divided into ten equallysized subframes 202. Other subframe durations such as including 0.5msec, 1 msec, 2 msec, and 5 msec may also be supported. Subframe(s) mayconsist of two or more slots (e.g. slots 206 and 207). For the exampleof FDD, 10 subframes may be available for downlink transmission and 10subframes may be available for uplink transmissions in each 10 msinterval. Uplink and downlink transmissions may be separated in thefrequency domain. Slot(s) may include a plurality of OFDM symbols 203.The number of OFDM symbols 203 in a slot 206 may depend on the cyclicprefix length and subcarrier spacing.

FIG. 3 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present invention. The resource grid structure intime 304 and frequency 305 is illustrated in FIG. 3. The quantity ofdownlink subcarriers or RBs (in this example 6 to 100 RBs) may depend,at least in part, on the downlink transmission bandwidth 306 configuredin the cell. The smallest radio resource unit may be called a resourceelement (e.g. 301). Resource elements may be grouped into resourceblocks (e.g. 302). Resource blocks may be grouped into larger radioresources called Resource Block Groups (RBG) (e.g. 303). The transmittedsignal in slot 206 may be described by one or several resource grids ofa plurality of subcarriers and a plurality of OFDM symbols. Resourceblocks may be used to describe the mapping of certain physical channelsto resource elements. Other pre-defined groupings of physical resourceelements may be implemented in the system depending on the radiotechnology. For example, 24 subcarriers may be grouped as a radio blockfor a duration of 5 msec. In an illustrative example, a resource blockmay correspond to one slot in the time domain and 180 kHz in thefrequency domain (for 15 KHz subcarrier bandwidth and 12 subcarriers).

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present invention. FIG. 5A shows an example uplink physical channel.The baseband signal representing the physical uplink shared channel mayperform the following processes. These functions are illustrated asexamples and it is anticipated that other mechanisms may be implementedin various embodiments. The functions may comprise scrambling,modulation of scrambled bits to generate complex-valued symbols, mappingof the complex-valued modulation symbols onto one or severaltransmission layers, transform precoding to generate complex-valuedsymbols, precoding of the complex-valued symbols, mapping of precodedcomplex-valued symbols to resource elements, generation ofcomplex-valued time-domain SC-FDMA signal for each antenna port, and/orthe like.

Example modulation and up-conversion to the carrier frequency of thecomplex-valued SC-FDMA baseband signal for each antenna port and/or thecomplex-valued PRACH baseband signal is shown in FIG. 5B. Filtering maybe employed prior to transmission.

An example structure for Downlink Transmissions is shown in FIG. 5C. Thebaseband signal representing a downlink physical channel may perform thefollowing processes. These functions are illustrated as examples and itis anticipated that other mechanisms may be implemented in variousembodiments. The functions include scrambling of coded bits in each ofthe codewords to be transmitted on a physical channel; modulation ofscrambled bits to generate complex-valued modulation symbols; mapping ofthe complex-valued modulation symbols onto one or several transmissionlayers; precoding of the complex-valued modulation symbols on each layerfor transmission on the antenna ports; mapping of complex-valuedmodulation symbols for each antenna port to resource elements;generation of complex-valued time-domain OFDM signal for each antennaport, and/or the like.

Example modulation and up-conversion to the carrier frequency of thecomplex-valued OFDM baseband signal for each antenna port is shown inFIG. 5D. Filtering may be employed prior to transmission.

FIG. 4 is an example block diagram of a base station 401 and a wirelessdevice 406, as per an aspect of an embodiment of the present invention.A communication network 400 may include at least one base station 401and at least one wireless device 406. The base station 401 may includeat least one communication interface 402, at least one processor 403,and at least one set of program code instructions 405 stored innon-transitory memory 404 and executable by the at least one processor403. The wireless device 406 may include at least one communicationinterface 407, at least one processor 408, and at least one set ofprogram code instructions 410 stored in non-transitory memory 409 andexecutable by the at least one processor 408. Communication interface402 in base station 401 may be configured to engage in communicationwith communication interface 407 in wireless device 406 via acommunication path that includes at least one wireless link 411.Wireless link 411 may be a bi-directional link. Communication interface407 in wireless device 406 may also be configured to engage in acommunication with communication interface 402 in base station 401. Basestation 401 and wireless device 406 may be configured to send andreceive data over wireless link 411 using multiple frequency carriers.According to some of the various aspects of embodiments, transceiver(s)may be employed. A transceiver is a device that includes both atransmitter and receiver. Transceivers may be employed in devices suchas wireless devices, base stations, relay nodes, and/or the like.Example embodiments for radio technology implemented in communicationinterface 402, 407 and wireless link 411 are illustrated are FIG. 1,FIG. 2, FIG. 3, FIG. 5, and associated text.

An interface may be a hardware interface, a firmware interface, asoftware interface, and/or a combination thereof. The hardware interfacemay include connectors, wires, electronic devices such as drivers,amplifiers, and/or the like. A software interface may include codestored in a memory device to implement protocol(s), protocol layers,communication drivers, device drivers, combinations thereof, and/or thelike. A firmware interface may include a combination of embeddedhardware and code stored in and/or in communication with a memory deviceto implement connections, electronic device operations, protocol(s),protocol layers, communication drivers, device drivers, hardwareoperations, combinations thereof, and/or the like.

The term configured may relate to the capacity of a device whether thedevice is in an operational or non-operational state. Configured mayalso refer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ornon-operational state. In other words, the hardware, software, firmware,registers, memory values, and/or the like may be “configured” within adevice, whether the device is in an operational or nonoperational state,to provide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics inthe device, whether the device is in an operational or non-operationalstate.

According to some of the various aspects of embodiments, an LTE networkmay include a multitude of base stations, providing a user planePDCP/RLC/MAC/PHY and control plane (RRC) protocol terminations towardsthe wireless device. The base station(s) may be interconnected withother base station(s) (e.g. employing an X2 interface). The basestations may also be connected employing, for example, an S1 interfaceto an EPC. For example, the base stations may be interconnected to theMME employing the S1-MME interface and to the S-G) employing the S1-Uinterface. The S1 interface may support a many-to-many relation betweenMMEs/Serving Gateways and base stations. A base station may include manysectors for example: 1, 2, 3, 4, or 6 sectors. A base station mayinclude many cells, for example, ranging from 1 to 50 cells or more. Acell may be categorized, for example, as a primary cell or secondarycell. At RRC connection establishment/re-establishment/handover, oneserving cell may provide the NAS (non-access stratum) mobilityinformation (e.g. TAI), and at RRC connection re-establishment/handover,one serving cell may provide the security input. This cell may bereferred to as the Primary Cell (PCell). In the downlink, the carriercorresponding to the PCell may be the Downlink Primary Component Carrier(DL PCC), while in the uplink, it may be the Uplink Primary ComponentCarrier (UL PCC). Depending on wireless device capabilities, SecondaryCells (SCells) may be configured to form together with the PCell a setof serving cells. In the downlink, the carrier corresponding to an SCellmay be a Downlink Secondary Component Carrier (DL SCC), while in theuplink, it may be an Uplink Secondary Component Carrier (UL SCC). AnSCell may or may not have an uplink carrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and a cell index. A carrier (downlinkor uplink) may belong to only one cell. The cell ID or Cell index mayalso identify the downlink carrier or uplink carrier of the cell(depending on the context it is used). In the specification, cell ID maybe equally referred to a carrier ID, and cell index may be referred tocarrier index. In implementation, the physical cell ID or cell index maybe assigned to a cell. A cell ID may be determined using asynchronization signal transmitted on a downlink carrier. A cell indexmay be determined using RRC messages. For example, when thespecification refers to a first physical cell ID for a first downlinkcarrier, the specification may mean the first physical cell ID is for acell comprising the first downlink carrier. The same concept may applyto, for example, carrier activation. When the specification indicatesthat a first carrier is activated, the specification may equally meanthat the cell comprising the first carrier is activated.

Embodiments may be configured to operate as needed. The disclosedmechanism may be performed when certain criteria are met, for example,in a wireless device, a base station, a radio environment, a network, acombination of the above, and/or the like. Example criteria may bebased, at least in part, on for example, traffic load, initial systemset up, packet sizes, traffic characteristics, a combination of theabove, and/or the like. When the one or more criteria are met, variousexample embodiments may be applied. Therefore, it may be possible toimplement example embodiments that selectively implement disclosedprotocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices may support multiple technologies, and/or multiple releases ofthe same technology. Wireless devices may have some specificcapability(ies) depending on its wireless device category and/orcapability(ies). A base station may comprise multiple sectors. When thisdisclosure refers to a base station communicating with a plurality ofwireless devices, this disclosure may refer to a subset of the totalwireless devices in a coverage area. This disclosure may refer to, forexample, a plurality of wireless devices of a given LTE release with agiven capability and in a given sector of the base station. Theplurality of wireless devices in this disclosure may refer to a selectedplurality of wireless devices, and/or a subset of total wireless devicesin a coverage area which perform according to disclosed methods, and/orthe like. There may be a plurality of wireless devices in a coveragearea that may not comply with the disclosed methods, for example,because those wireless devices perform based on older releases of LTEtechnology.

LTE based V2X services may be V2V or vehicle-to-vehicle, which maycomprise direct communication between two or more vehicles. In anexample embodiment, this communication may be one-to-one. In an exampleembodiment, this communication may be one-to-many FIG. 6 shows only theexample embodiment when the communication is one-to-one. V2V may be vianetwork communication between 2 or more vehicles. In an exampleembodiment, this communication may be one-to-one. In an exampleembodiment, this communication may be one-to-many FIG. 7 shows only theexample embodiment when the communication is one-to-many

LTE based V2X services may comprise V2P or vehicle-to-pedestrian, whichmay comprise direct communications between vehicles and devices ofmobile users. In an example embodiment, this communication may beone-to-one as shown in FIG. 8A. In an example embodiment, thiscommunication may be one-to-many as shown in FIG. 8B. V2P via networkcommunications between vehicles and devices of mobile users. In anexample embodiment, this communication may be one-to-one as shown inFIG. 9A. In an example embodiment, this communication may be one-to-manyas shown in FIG. 9B.

LTE based V2X services may comprise V2I/N orvehicle-to-infrastructure/network. LTE based communications betweenvehicles and roadside units (RSUs) or infrastructure may comprise aneNB-type RSU (infrastructure) as shown in FIG. 10A and FIG. 10B. In oneexample embodiment, communications between the RSU/network and thevehicle may comprise one-to-one communications as shown in FIG. 10A. Inan example embodiment, the communications between the RSU/network andthe vehicle may comprise one-to-many communications as shown in FIG.10B.

In an example embodiment, an RSU may comprise a UE-type RSU and relaythe UE to the network as shown in the FIG. 11A and FIG. 11B. In oneexample embodiment, communications between the RSU and the vehicle maycomprise one-to-one communications as shown in FIG. 11A. In an exampleembodiment, the communications between the RSU and the vehicle maycomprise one-to-many communications as shown in FIG. 11B.

Other combinations of LTE based V2I/V orvehicle-to-infrastructure/vehicle may be employed. For example, anembodiment RSU may comprise a UE-type RSU and relay communications fromone vehicle to another vehicle as shown in FIG. 12A and FIG. 12B. In oneexample embodiment, communications between the RSU and the vehicle maycomprise one-to-one communications as shown in FIG. 12A. In an exampleembodiment, the communications between the RSU and the vehicle maycomprise one-to-many communications as shown in FIG. 12B.

FIG. 13A and FIG. 13B show example V2I/P orvehicle-to-infrastructure/pedestrian communications through an RSU. Inan example embodiment, RSU may comprise UE-type RSU and relay thevehicle to pedestrians as shown in. In one example embodiment,communications between the RSU and the vehicle may be one-to-one asshown in FIG. 13A. In an example embodiment, the communications betweenthe RSU and the vehicle may be one-to-many as shown in FIG. 13 B.

In an example embodiment, the architecture of V2X may be as shown inFIG. 14 where, MME=mobility management entity, HSS=home subscriberserver, PLMN=public land mobile network, E-UTRAN=evolved universalterrestrial access network, UE=user equipment, S-GW=serving gateway, andP-GW=public directory number gateway.

In one example embodiment, user equipment (UE) with the application V2Xmay be a pedestrian and may get credentials from V2X application server(AS) and V2X control function for discovery procedure on PC5. In oneexample embodiment, user equipment (UE) with the application V2X may bea vehicle and may get credentials from V2X application server (AS) andV2X control function for discovery procedure on PC5. In one exampleembodiment, user equipment (UE) with the application V2X may be an RSUand may get credentials from V2X application server (AS) and V2X controlfunction for discovery procedure on PC5.

In one example embodiment, the first UE with the application V2X maycommunicate with the second UE with the application V2X by means foraccessing the V2X control function and V2X AS. In one exampleembodiment, the first UE with the application V2X may communicate withthe second UE with the application V2X by means for using PC5 interface.In one example embodiment, the first UE with the application V2X maycommunicate with the second UE with the application V2X by means foraccessing the V2X control function and V2X AS through a third UE withthe application V2X. In one example embodiment, the first UE with theapplication V2X may communicate with the second UE with the applicationV2X through the third UE with application V2X by means for firstaccessing the V2X control function and the V2X AS to access the third UEwith the application V2X. In one example embodiment, the first UE withapplication V2X may communicate with the second UE with the applicationV2X through the third UE with the application V2X.

In one example embodiment, the V2X UEs may register with IP MultimediaSubsystem (IMS) network. At the time of registration to the IMS network,a V2X UE may include its supported IMS communication service identifier(ICSI) values for the IMS communication services it intends to use. TheV2X UE may register its supported IMS application reference identifier(IARI) values for the IMS applications it intends to use at the time ofIMS registration as described here. The V2X UE may include supportedICSI values in a g.3gpp.icsi-ref media feature tag for the IMScommunication services it intends to use, and IARI values, for the IMSapplications it intends to use in a g.3gpp.iari-ref media feature tag.The UE may include the media feature tags for supported streaming mediatypes.

The flow diagram in FIG. 15 shows an example embodiment for IMSregistration of a V2X UE. FIG. 15 shows, that a V2X UE may send asession initial protocol (SIP) REGISTER request containing a V2X featuretag in a contact header field towards the proxy call session controlfunction (P-CSCF) in the visiting network. P-CSCF may use the V2X UE'sID to locate the interrogating call session control function (I-CSCF) inthe home network by domain name system (DNS) query. I-CSCF in the homenetwork may select suitable serving call session control function(S-CSCF) with help of HSS. S-CSCF may challenge the registration byrequesting an authentication. If the authentication information is notvalid, S-CSCF may get it from HSS. V2X UE may provide an authenticationresponse and may send a SIP REGISTER request containing authenticationresponse and the V2X feature tag in the contact header towards theP-CSCF in the visiting network. P-CSCF may use the V2X UE's ID to locatethe I-CSCF in the home network by DNS query. I-CSCF in the home networkmay select suitable S-CSCF with help of HSS. S-CSCF may authenticate theV2X UE and may send registration notification to the HSS and may receivethe V2X user profile from the HSS. The V2X user profile may be used fora 3rd party register to the V2X application server (AS), and S-CSCF mayrespond with OK to the V2X UE.

In one example embodiment, a V2X UE may comprise capabilities such ascapabilities for vehicle, pedestrian, or RSU (infrastructure). To avoidor reduce any possible compatibility issues, new service or applicationidentifiers may be implemented for the additional capabilities. In anexample embodiment, IMS communication service identifiers (ICSIs) may beemployed at the time of IMS registration to indicate different types forV2X UE e.g. pedestrian, vehicle, RSU. One or more IMS service parametersmay be communicated during the registration process to indicate at leastone V2X UE capability to a network server, e.g. a proxy server, aregistrar server.

In one example embodiment, a V2X UE may comprise capabilities forvehicle-to-vehicle service, vehicle-to-pedestrian service,vehicle-to-infrastructure service, and/or vehicle-to-network servicecapabilities. To communicate this with the network, the V2X UE may needto employ ICSs at the time of the registration to the network. One ormore IMS service parameters may be communicated during the registrationprocess to indicate at least one V2X UE capability to a network server,e.g. a proxy server, a registrar server.

In one example embodiment, the V2X UE may comprise capabilities for anemergency vehicle-to-vehicle service, emergency vehicle-to-pedestrianservice, emergency vehicle-to-infrastructure service, and/or emergencyvehicle-to-network service capabilities. To communicate this with thenetwork, the V2X UE may employ ICSs at the time of the registration tothe network. One or more IMS service parameters may be communicatedduring the registration process to indicate at least one V2X UEcapability to a network server, e.g. a proxy server, a registrar server.

The wireless device may register one or more IMS communication serviceidentifiers (ICSIs) of warning system (e.g. V2X in a wireless network).One of the one or more ICSIs may indicate at least one of pedestrian,vehicle, infrastructure, vehicle-to-vehicle service,vehicle-to-pedestrian service, vehicle-to-infrastructure service, and/orvehicle-to-network service capabilities of the wireless device. ICSI maybe in the form of a media feature tag. A feature tag may indicate one ormore capability of the wireless device. For example, a specific featuretag, such as 3gpp-service.ims.icsi.v2x.vehicle may indicate V2X UE maybe a vehicle or 3gpp-service.ims.icsi. V2n may indicate a V2X UE mayhave a capability for the service of communication between a vehicle anda network or 3gpp-service.ims.icsi.emergency.v2n may have a capabilityfor a service of communication between a high priority vehicle such asambulance or police and a network. These are examples and other featurestag names may be used. One or more ICSI may indicate a combination of atleast two of: pedestrian, vehicle, infrastructure, vehicle-to-vehicleservice, vehicle-to-pedestrian service, vehicle-to-infrastructureservice, and/or vehicle-to-network service capabilities of the wirelessV2X device. For example, a feature tag 3gpp-service.ims.icsi.v2x mayindicate capability for V2X which may be vehicle, pedestrian, and/orinfrastructure or v2x services which may be vehicle-to-vehicle service,vehicle-to-pedestrian service, vehicle-to-infrastructure service, and/orvehicle-to-network service.

In one example embodiment, one or more additional parameters may beincluded in the registration message along with a feature tag toindicate the V2X device capability or a combination of one or morecapabilities of the V2X device.

In one example implementation, the V2X device may transmit theregistration message to a UE relay which relays to message to a networknode. The wireless device may discover the UE relay using discoverymodel A or model B. In an example, the UE relay may decode theregistration message and may update the message headers beforeretransmitting the message. The UE relay may update the source anddestination address in the registration message.

In one example embodiment, the registration message may further registerone or more IMS application reference identifiers (IARIs). One of theone or more IARIs may indicate at least one of: a pedestrian, vehicle,infrastructure, vehicle-to-vehicle application, vehicle-to-pedestrianapplication, vehicle-to-infrastructure application, and/orvehicle-to-network application capabilities of the wireless V2X device.In one example one or more of the one or more IARIs may indicate atleast one of: emergency case of the pedestrian, vehicle, infrastructure,vehicle-to-vehicle application, vehicle-to-pedestrian application,vehicle-to-infrastructure application, and/or vehicle-to-networkapplication capabilities of the wireless V2X device. IARI may be in theform of a media feature tag. A feature tag may indicate one or morecapability of the V2X device. For example, a specific feature tag, suchas 3gpp-application.ims.iari.v2x.vehicle may indicate V2X UE havingvehicle capability or 3gpp-application.imsi.iari.v2n may indicate V2X UEmay have capability for the application vehicle-to-network communicationor 3gpp-application.imsi.iari.emergency.v2n may indicate V2X UE may havecapability for the application a high priority vehicle such as ambulanceor police to the network communication. These are examples and otherfeatures tag names may be used. One or more IARI may indicate acombination of at least two of pedestrian, vehicle, infrastructure,vehicle-to-vehicle application, vehicle-to-pedestrian application,vehicle-to-infrastructure application, and/or vehicle-to-networkapplication capabilities of the V2X device. For example, a feature tag3gpp-application.ims.iari.v2x may indicate capability for V2X which maybe vehicle, pedestrian, infrastructure, vehicle-to-vehicle application,vehicle-to-pedestrian application, vehicle-to-infrastructureapplication, and/or vehicle-to-network application.

In one example embodiment, the wireless device may register one or moreIMS application reference identifiers (IARIs) of V2X in a wirelessnetwork. One of the one or more IARIs may indicate at least one ofpedestrian, vehicle, infrastructure, vehicle-to-vehicle application,vehicle-to-pedestrian application, vehicle-to-infrastructureapplication, and/or vehicle-to-network application capabilities of theV2X device. In one example, the one or more IARIs may indicate acombination of at least two of pedestrian, vehicle, infrastructure,vehicle-to-vehicle application, vehicle-to-pedestrian application,vehicle-to-infrastructure application, and/or vehicle-to-networkapplication capabilities of the V2X device. The V2X device may furtherregistering one or more IMS communication service identifiers (ICSIs).One of the one or more ICSIs indicates at least one of pedestrian,vehicle, infrastructure, vehicle-to-vehicle application,vehicle-to-pedestrian application, vehicle-to-infrastructureapplication, and/or vehicle-to-network application capabilities of thewireless device.

In one example embodiment, the V2X UE may register one or more IMSservice parameters of V2X in a wireless network. The one or more IMSservice parameters may indicate a combination of at least two ofpedestrian, vehicle, infrastructure, vehicle-to-vehicle,vehicle-to-pedestrian, vehicle-to-infrastructure, and/orvehicle-to-network capabilities of the V2X UE. The one or more IMSservice parameters may indicate at least one of pedestrian, vehicle,infrastructure, vehicle-to-vehicle, vehicle-to-pedestrian,vehicle-to-infrastructure, and/or vehicle-to-network capabilities of theV2X UE.

One example embodiment may include enhanced service identifiersrepresenting new services such as 3gpp-service.ims.icsi.v2x,3gpp-service.ims.icsi.v2x.pedestrian, 3gpp-service.ims.icsi.v2x.vehicle,3gpp-service.ims.icsi.v2x.infrastructure,3gpp-service.ims.icsi.v2x.emergency,3gpp-service.ims.icsi.v2x.emergency.pedestrian,3gpp-service.ims.icsi.v2x.emregency.vehicle, and3gpp-service.ims.icsi.v2x.emregency.infrastructure. One exampleembodiment may include enhanced service identifiers representing newservices such as 3gpp-service.ims.icsi.v2i, 3gpp-service.ims.icsi.v2n,3gpp-service.ims.icsi.v2p, 3gpp-service.ims.icsi.v2v,3gpp-service.ims.icsi.v2i.emregency,3gpp-service.ims.icsi.v2n.emregency,3gpp-service.ims.icsi.v2p.emregency, and3gpp-service.ims.icsi.v2v.emregency. One example embodiment may includeenhanced application identifiers that represent applications for the V2Xservice 3gpp-application.ims.iari.v2x,3gpp-application.ims.iari.v2x.pedestrian,3gpp-application.ims.iari.v2x.vehicle,3gpp-application.ims.iari.v2x.infrastructure,3gpp-application.ims.iari.v2x.emergency,3gpp-application.ims.iari.v2x.emeregency.pedestrian,3gpp-application.ims.iari.v2x.emeregncy.vehicle, and3gpp-application.ims.iari.v2x.emergency.infrastructure. One exampleembodiment may include enhanced application identifiers that representapplications for the V2X service 3gpp-application.ims.iari.v2i,3gpp-application.ims.iari.v2n, 3gpp-application.ims.iari.v2p,3gpp-application.ims.iari.v2v, 3gpp-application.ims.iari.v2i.emregency,3gpp-application.ims.iari.v2n.emregency,3gpp-application.ims.iari.v2p.emregency,3gpp-application.ims.iari.v2v.emregency.

In an example, an embodiment may register one or more IMS communicationidentifiers (ICSI) for capabilities such as for being V2X UE capable ina wireless network. An example embodiment may register one or more IMScommunication identifiers (ICSI) for capabilities such as for beingpedestrian capable V2X UE in a wireless network. An example embodimentmay register one or more IMS communication identifiers (ICSI) forcapabilities such as for being vehicle capable V2X UE in a wirelessnetwork. An example embodiment may register one or more IMScommunication identifiers (ICSI) for capabilities such as for beinginfrastructure capable V2X UE in a wireless network. An exampleembodiment may register one or more IMS communication identifiers (ICSI)for capabilities such as for being emergency V2X UE capable in awireless network. An example embodiment may register one or more IMScommunication identifiers (ICSI) for capabilities such as for beingemergency pedestrian capable V2X UE in a wireless network. An exampleembodiment may register one or more IMS communication identifiers (ICSI)for capabilities such as for being emergency vehicle capable V2X UE in awireless network. An example embodiment may register one or more IMScommunication identifiers (ICSI) for capabilities such as for beingemergency infrastructure capable V2X UE in a wireless network. Anexample embodiment may register one or more IMS communicationidentifiers (ICSI) for capabilities such as for beingvehicle-to-pedestrian service capable V2X UE in a wireless network. Anexample embodiment may register one or more IMS communicationidentifiers (ICSI) for capabilities such as for being vehicle-to-vehicleservice capable V2X UE in a wireless network. An example embodiment mayregister one or more IMS communication identifiers (ICSI) forcapabilities such as for being vehicle-to-infrastructure service capableV2X UE in a wireless network. An example embodiment may register one ormore IMS communication identifiers (ICSI) for capabilities such as forbeing vehicle-to-network service capable V2X UE in a wireless network.An example embodiment may register one or more IMS communicationidentifiers (ICSI) for capabilities such as for being emergencyvehicle-to-pedestrian service capable V2X UE in a wireless network. Anexample embodiment may register one or more IMS communicationidentifiers (ICSI) for capabilities such as for being emergencyvehicle-to-vehicle service capable V2X UE in a wireless network. Anexample embodiment may register one or more IMS communicationidentifiers (ICSI) for capabilities such as for being emergencyvehicle-to-infrastructure service capable V2X UE in a wireless network.An example embodiment may register one or more IMS communicationidentifiers (ICSI) for capabilities such as for being emergencyvehicle-to-network service capable V2X UE in a wireless network.

An example embodiment may register one or more IMS communicationidentifiers (ICSI) for capabilities such as for being pedestrian,vehicle, infrastructure, vehicle-to-vehicle service,vehicle-to-pedestrian service, vehicle-to-infrastructure service, and/orvehicle-to-network service capable V2X UE in a wireless network.

An example embodiment may register one or more IMS communicationidentifiers (ICSI) for capabilities such as for being emergencypedestrian, emergency vehicle, emergency infrastructure, emergencyvehicle-to-vehicle service, emergency vehicle-to-pedestrian service,emergency vehicle-to-infrastructure service, and/or emergencyvehicle-to-network service capable V2X UE in a wireless network.

An example embodiment may register one or more IMS application referenceidentifiers (IARI) for capabilities such as for being V2X UE capable ina wireless network. An example embodiment may register one or more IMSapplication reference identifiers (IARI) for capabilities such as forbeing pedestrian capable V2X UE in a wireless network. An exampleembodiment may register one or more IMS application referenceidentifiers (IARI) for capabilities such as for being vehicle capableV2X UE in a wireless network. An example embodiment may register one ormore IMS application reference identifiers (IARI) for capabilities suchas for being infrastructure capable V2X UE in a wireless network. Anexample embodiment may register one or more IMS application referenceidentifiers (IARI) for capabilities such as for beingvehicle-to-pedestrian application capable V2X UE in a wireless network.An example embodiment may register one or more IMS application referenceidentifiers (IARI) for capabilities such as for being vehicle-to-vehicleapplication capable V2X UE in a wireless network. An example embodimentmay register one or more IMS application reference identifiers (IARI)for capabilities such as for being vehicle-to-infrastructure applicationcapable V2X UE in a wireless network. An example embodiment may registerone or more IMS application reference identifiers (IARI) forcapabilities such as for being vehicle-to-network application capableV2X UE in a wireless network. An example embodiment may register one ormore IMS application reference identifiers (IARI) for capabilities suchas for being emergency V2X UE capable in a wireless network. An exampleembodiment may register one or more IMS application referenceidentifiers (IARI) for capabilities such as for being emergencypedestrian capable V2X UE in a wireless network. An example embodimentmay register one or more IMS application reference identifiers (IARI)for capabilities such as for being emergency vehicle capable V2X UE in awireless network. An example embodiment may register one or more IMSapplication reference identifiers (IARI) for capabilities such as forbeing emergency infrastructure capable V2X UE in a wireless network. Anexample embodiment may register one or more IMS application referenceidentifiers (IARI) for capabilities such as for being emergencyvehicle-to-pedestrian application capable V2X UE in a wireless network.An example embodiment may register one or more IMS application referenceidentifiers (IARI) for capabilities such as for being emergencyvehicle-to-vehicle application capable V2X UE in a wireless network. Anexample embodiment may register one or more IMS application referenceidentifiers (IARI) for capabilities such as for being emergencyvehicle-to-infrastructure application capable V2X UE in a wirelessnetwork. An example embodiment may register one or more IMS applicationreference identifiers (IARI) for capabilities such as for beingemergency vehicle-to-network application capable V2X UE in a wirelessnetwork.

An example embodiment may register one or more IMS application referenceidentifiers (IARI) for capabilities such as for being pedestrian,vehicle, infrastructure, vehicle-to-vehicle application,vehicle-to-pedestrian application, vehicle-to-infrastructureapplication, and/or vehicle-to-network application capable V2X UE in awireless network.

An example embodiment may register one or more IMS application referenceidentifiers (IARI) for capabilities such as for being emergencypedestrian, emergency vehicle, emergency infrastructure, emergencyvehicle-to-vehicle application, emergency vehicle-to-pedestrianapplication, emergency vehicle-to-infrastructure application, and/oremergency vehicle-to-network application capable V2X UE in a wirelessnetwork.

In an example embodiment, a V2X UE may proxy one or other V2X UEs forICSI registration and/or IARI registration to the IMS network with nomodification to the register message. In an example embodiment, a V2X UEmay proxy one or many other V2X UEs for ICSI registration and/or IARIregistration to the IMS network with modification to the header of theregister message. In an example embodiment, a V2X UE may proxy one ormany other V2X UEs for ICSI registration and/or IARI registration to theIMS network with modification to the body of the register message. In anexample embodiment, a V2X UE may proxy one or many other V2X UEs forICSI registration and/or IARI registration to the IMS network withmodification to the header and the body of the register message. Othercombination for creating feature tags for service and applicationidentifiers for V2X may be implemented.

FIG. 16 shows flow diagram for an example embodiment of an IMSregistration for a V2X UE. FIG. 16 shows that V2X UE may include the V2Xrelated ICSI and IARI which it may intent to use to its contact headerfield of the register message when registering to the IMS network. TheIMS network may locate the most suitable S-CSCF for this registrationand may forward the registration request to that S-CSCF, S-CSCF maychallenge the V2X UE by sending authentication request to the UE, V2X UEmay respond to the authentication request, and S-CSCF 3rd part mayregister the UE to the V2X AS.

A wireless device may register one or more IMS communication serviceidentifiers (ICSIs) for V2X in a wireless network. One of the one ormore ICSIs may indicate at least one of pedestrian, vehicle, and/orinfrastructure capabilities of the V2X device.

3GPP has defined a warning system based on vehicle-to-vehicle (V2V),vehicle-to-pedestrian (V2P), vehicle-to-infrastructure (V2I), andvehicle to network (V2N). Due to different use cases, these new featuresmay require new capabilities and may result in compatibility issue atthe time of communications. In some example cases, network (e.g. theregistrar or application servers, and/or third party applicationservers, and/or other network entities) may need to know the V2X UE'scapabilities in terms of supported services and applications.

A network node may transmit a request to a registrar and/or network nodestoring V2X UE capability and request for V2X UE capabilities. Thenetwork node may transmit a response message to the requester (directlyor indirectly) indicating the V2X UE capabilities of the UE. The networknodes may communicate (transmit/receive) the V2X user's capabilities byexchanging SIP message(s) (e.g. SIP MESSAGE method).

The network node may transmit a SIP message (e.g. SIP MESSAGE method) tothe UE to set up a session to stream a video clip to the V2X UE. Thus,the network may need to know if the V2X UE has the capability to receiveit. The network node may transmit a SIP message (e.g. SIP MESSAGEmethod) to the UE to set up a session to send information aboutmulticast bearer and the related ports for media reception. Thus, thenetwork may need to know about the V2X UE's capabilities to receive themulticast media.

A third-party entity may like to get a V2X UE's capabilities from theoperator's network where V2X UE has registered to, in order to e.g.provide a service or application. A third-party entity may transmit aSIP message (e.g. SIP MESSAGE method) to the UE to set up a session.Therefore, the network must know the V2X UE's capabilities to providethis information to the third-party entity. The V2X UE may response tothe SIP message. The network/third party may subsequently startcommunicating and transmitting/receiving data to/from the V2X UE.

For a new dialog or standalone transaction in one example embodiment,once the V2X UEs are all registered to the IMS network and if a V2X UEmay like to request a new dialog or standalone transaction, the V2X UEmay include all its supported ICSI values for the IMS communicationservices it may intend to use to all other SIP methods than the SIPREGISTER method. The V2X UE may include all its supported IARI valuesfor the IMS applications it may intend to use to those methods.

If this is a request for a new dialog, the Contact header field may bepopulated as a contact header value which may be a public GRUU value, atemporary GRUU value, or SIP URI containing the contact address of theV2X UE; an “ob” SIP URI parameter; an ICSI that the V2X UE may includein a g.3gpp.icsi-ref media feature tag; and an IARI that the V2X UE mayinclude in a g.3gpp.iari-ref media feature tag.

If a V2X UE receives ICSI values corresponding to the IMS communicationservices that the network provides to the user, if the V2X UE constructsa request for a new dialog or standalone transaction and the request isrelated to one of the ICSI values, the V2X UE may populate aP-Preferred-Service header field with one of the ICSI values.

In construction of the same request for a new dialog and standalonetransaction, the V2X UE may populate an Accept-Contact header fieldcomprising an ICSI value which may differ from the one added toP-Preferred-Service header field. In construction of a request for a newdialog or standalone transaction, the V2X UE may populate anAccept-Contact header field comprising an IARI value if an IMSapplication indicates that an IARI is to be included in a request

The V2X UE may modify the established dialog capabilities by, forexample, adding a media or requesting a supplementary service if themodification is defined for the IMS communication service. If themodification is not defined for that IMS communication service, the V2XUE may initiate a new dialog.

In one example embodiment, a trusted application server may insertP-Asserted-Service header field in a request for a new dialog orstandalone transaction and may include ICSI value for the related IMScommunication service to that header field. In one example embodiment,an untrusted application server may insert P-Preferred-Service headerfield in a request for a new dialog or standalone transaction and mayinclude ICSI value for the related IMS communication service to thatheader field.

In an example embodiment, if an AS acts as an initiating back-to-backuser agent (B2BUA) or a routing B2BUA and may be sending a request for adialog or a standalone transaction by including an ICSI value and one ormore IARI values in the Accept-Contact header field, if there are ICSIvalue and IARI value(s) for the IMS communication service and IMSapplications.

The flow diagram in the example embodiment in FIG. 17 shows a V2X UEsends a request to V2X AS. FIG. 17 shows a V2X UE initiating a SIPrequest towards a V2X AS for a certain service or information. In oneexample embodiment, the SIP request may comprise a V2X feature tag inthe Contact header field. In one example embodiment, the SIP request maycomprise a V2X feature tag in the Contact header field and theAccept-Contact header field indicating the V2X service may be requiredfor that SIP request. P-CSCF may use the V2X UE's ID to locate I-CSCF inthe home network by DNS query. I-CSCF in the home network may selectsuitable S-CSCF with help of HSS. S-CSCF may validate the serviceprofile of the V2X UE and may evaluate the filter criteria. It maythereafter forward the invite towards the V2X AS. The V2X AS may analyzethe feature tag and may send an appropriate response back towards theV2X UE.

In an example embodiment, V2X communication messages may comprisecapabilities such as capabilities for vehicle, pedestrian, and/orinfrastructure. To avoid or reduce any possible compatibility issues,new service or application identifiers may be implemented for theadditional capabilities. According to an example embodiment, ICSIs maybe employed at the time of establishing new dialog or standalonetransaction to indicate different capabilities for V2X e.g. pedestrian,vehicle, infrastructure, vehicle-to-vehicle, vehicle-to-pedestrian,vehicle-to-infrastructure, and/or vehicle-to-network. One or more IMSservice parameters may be communicated during the new dialogestablishment procedure and/or standalone transaction process toindicate at least one V2X capability to a network server, e.g. a proxyserver, a registrar server.

According to an example embodiment, ICSIs may be employed at the time ofestablishing new dialog or standalone transaction to indicate differentcapabilities for V2X, for example, emergency pedestrian, emergencyvehicle, emergency infrastructure, emergency vehicle-to-vehicle,emergency vehicle-to-pedestrian, emergency vehicle-to-infrastructure,and/or emergency vehicle-to-network. One or more IMS service parametersmay be communicated during the new dialog establishment procedure and/orstandalone transaction process to indicate at least one V2X capabilityto a network server (e.g. a proxy server, a registrar server).

The V2X UE may employ one or more IMS communication service identifiers(ICSIs) of a warning system (e.g. V2X for new dialogs establishment orstandalone transactions in a wireless network). One of the one or moreICSIs may indicate at least one of pedestrian, vehicle and/orinfrastructure capabilities of the V2X device. ICSI may be in the formof a media feature tag. A feature tag may indicate one or morecapability of the V2X device. For example, a specific feature tag, suchas 3gpp-service.ims.icsi.v2x.rsu may indicate infrastructure capabilityof the V2X device or 3gpp-service.ims.icsi.v2n may indicatevehicle-to-network service capability or3gpp-service.ims.icsi.emeregncy.v2n may indicate emergencyvehicle-to-network service capability. These are examples, otherfeatures tag names may be used. One or more ICSI may indicate acombination of at least two of pedestrian, vehicle, infrastructure,vehicle-to-vehicle service, vehicle-to-pedestrian service,vehicle-to-infrastructure service, and/or vehicle-to-network servicecapabilities of the V2X device. For example, a feature tag3gpp-service.ims.icsi.v2x, may indicate capability for vehicle,pedestrian, infrastructure, vehicle-to-vehicle service,vehicle-to-pedestrian service, vehicle-to-infrastructure service, and/orvehicle-to-network service.

One or more ICSI may indicate a combination of at least two of emergencypedestrian, emergency vehicle, emergency infrastructure, emergencyvehicle-to-vehicle service, emergency vehicle-to-pedestrian service,emergency vehicle-to-infrastructure service, and/or emergencyvehicle-to-network service capabilities of the V2X device. For example,a feature tag 3gpp-service.ims.icsi.emergency.v2x, may indicatecapability for emergency vehicle, emergency pedestrian, emergencyinfrastructure, emergency vehicle-to-vehicle service, emergencyvehicle-to-pedestrian service, emergency vehicle-to-infrastructureservice, and/or emergency vehicle-to-network service.

In another example, one or more additional parameters may be included inthe new dialog establishment or a standalone transaction along with afeature tag to indicate the V2X device capability or a combination ofone or more capabilities of the V2X device.

In an implementation, the V2X device may transmit the message toestablish a new dialog or as a standalone transaction to a UE relay viaPC5 which may relay the message to a network node. The V2X device maydiscover the UE relay using discovery model A or model B. In an example,the UE relay may decode the message for new dialog establishment or forthe standalone transition and may update the message headers beforeretransmitting the message. The UE relay may update the source anddestination address in the message for the new dialog and standalonetransaction.

In an example embodiment, the message for the new dialog and thestandalone transaction may further employ one or more IMS applicationreference identifiers (IARIs). One of the one or more IARIs may indicateat least one of pedestrian, vehicle, and/or infrastructure capabilitiesof the wireless V2X device. IARI may be in the form of a media featuretag. A feature tag may indicate one or more capability of the V2Xdevice. For example, a specific feature tag such as3gpp-application.ims.iari.v2x.vehicle may indicate V2X UE having vehiclecapability or 3gpp-application.ims.iari.v2n may indicatevehicle-to-network application capability or3gpp-application.ims.iari.emergency.v2n may indicate high priorityvehicle such as ambulance or police to-network application capability.These are examples and other features tag names may be used. One or moreIARI may indicate a combination of at least two of pedestrian, vehicle,infrastructure, vehicle-to-vehicle application, vehicle-to-pedestrianapplication, vehicle-to-infrastructure application, and/orvehicle-to-network application capabilities of the V2X device. Forexample, a feature tag 3gpp-application.ims.iari.v2x may indicatecapability for V2X which may be vehicle, pedestrian, infrastructure,vehicle-to-vehicle application, vehicle-to-pedestrian application,vehicle-to-infrastructure application, and/or vehicle-to-networkapplication.

One or more IARI may indicate a combination of at least two of emergencypedestrian, emergency vehicle, emergency infrastructure, emergencyvehicle-to-vehicle application, emergency vehicle-to-pedestrianapplication, emergency vehicle-to-infrastructure application, and/oremergency vehicle-to-network application capabilities of the V2X device.For example, a feature tag 3gpp-application.ims.iari.emregency.v2x mayindicate capability for V2X which may be emergency vehicle, emergencypedestrian, emergency infrastructure, emergency vehicle-to-vehicleapplication, emergency vehicle-to-pedestrian application, emergencyvehicle-to-infrastructure application, and/or emergencyvehicle-to-network application.

In an example embodiment, the V2X device may employ one or more IMSapplication reference identifiers (IARIs) of V2X in a wireless networkfor establishment of a new dialog or for standalone message. One of theone or more IARIs may indicate at least one of vehicle, pedestrian,infrastructure, vehicle-to-vehicle application, vehicle-to-pedestrianapplication, vehicle-to-infrastructure application, and/orvehicle-to-network application capabilities of the V2X UE. In an exampleembodiment, the one or more IARIs may indicate a combination of at leasttwo of pedestrian, vehicle, infrastructure, vehicle-to-vehicleapplication, vehicle-to-pedestrian application,vehicle-to-infrastructure application, and/or vehicle-to-networkapplication capabilities of the wireless device. The wireless device mayfurther employ one or more IMS communication service identifiers (ICSIs)for establishing new dialog or standalone message. One of the one ormore ICSIs indicates at least one of pedestrian, vehicle,infrastructure, vehicle-to-vehicle service, vehicle-to-pedestrianservice, vehicle-to-infrastructure service, and/or vehicle-to-networkservice capabilities of the V2X UE.

In an example, the V2X UE may employ one or more IMS service parametersof V2X in a wireless network for establishing a new dialog or astandalone message. The one or more IMS service parameters may indicatea combination of at least two of pedestrian, vehicle, infrastructure,vehicle-to-vehicle, vehicle-to-pedestrian, vehicle-to-infrastructure,and/or vehicle-to-network capabilities of the V2X UE. The one or moreIMS service parameters indicate at least one of pedestrian, vehicle,infrastructure, vehicle-to-vehicle, vehicle-to-pedestrian,vehicle-to-infrastructure, and/or vehicle-to-network capabilities of theV2X UE.

An example embodiment may include enhanced service identifiersrepresenting new services such as 3gpp-service.ims.icsi.v2x,3gpp-service.ims.icsi.v2x.pedestrian, 3gpp-service.ims.icsi.v2x.vehicle,3gpp-service.ims.icsi.v2x.infrastructure,3gpp-service.ims.icsi.v2x.emergency,3gpp-service.ims.icsi.v2x.pedestrian.emergency,3gpp-service.ims.icsi.v2x.vehicle.emergency, and3gpp-service.ims.icsi.v2x.infrastructure.emergency. In one exampleembodiment, the embodiments may include enhanced service identifiersrepresenting new services such as 3gpp-service.ims.icsi.v2i,3gpp-service.ims.icsi.v2n, 3gpp-service.ims.icsi.v2p,3gpp-service.ims.icsi.v2v, 3gpp-service.ims.icsi.v2i.emergency,3gpp-service.ims.icsi.v2n.emergency,3gpp-service.ims.icsi.v2p.emergency, and3gpp-service.ims.icsi.v2v.emergency. An example embodiment may includeenhanced application identifiers that represent applications for the V2Xservice 3gpp-application.ims.iari.v2x,3gpp-application.ims.iari.v2x.pedestrian,3gpp-application.ims.iari.v2x.vehicle,3gpp-application.ims.iari.v2x.infrastructure,3gpp-application.ims.iari.v2x.emergency,3gpp-application.ims.iari.v2x.emergency.pedestrian,3gpp-application.ims.iari.v2x.emergency.vehicle, and3gpp-application.ims.iari.v2x.emergency.infrastructure. In one exampleembodiment, the embodiments may include enhanced application identifiersthat represent applications for the V2X service3gpp-application.ims.iari.v2i, 3gpp-application.ims.iari.v2n,3gpp-application.ims.iari.v2p, 3gpp-application.ims.iari.v2v,3gpp-application.ims.iari.emergency.v2i,3gpp-application.ims.iari.emergency.v2n,3gpp-application.ims.iari.emergency.v2p, and3gpp-application.ims.iari.emergency.v2v.

In an example embodiment, the message for a new dialog establishment ora standalone message may employ one or more IMS communicationidentifiers (ICSI) for capabilities such as for being V2X UE capable ina wireless network. In an example embodiment, the message for a newdialog establishment or a standalone message may employ one or more IMScommunication identifiers (ICSI) for capabilities such as for beingpedestrian capable V2X UE in a wireless network. In an exampleembodiment, the message for a new dialog establishment or a standalonemessage may employ one or more IMS communication identifiers (ICSI) forcapabilities such as for being vehicle capable V2X UE in a wirelessnetwork. In an example embodiment, the message for a new dialogestablishment or a standalone message may employ one or more IMScommunication identifiers (ICSI) for capabilities such as for beinginfrastructure capable V2X UE in a wireless network. In an exampleembodiment, the message for a new dialog establishment or a standalonemessage may employ one or more IMS communication identifiers (ICSI) forcapabilities such as for being vehicle-to-pedestrian service capable V2XUE in a wireless network.

In an example embodiment, the message for a new dialog establishment ora standalone message may employ one or more IMS communicationidentifiers (ICSI) for capabilities such as for being vehicle-to-vehicleservice capable V2X UE in a wireless network. In an example embodiment,the message for a new dialog establishment or a standalone message mayemploy one or more IMS communication identifiers (ICSI) for capabilitiessuch as for being vehicle-to-infrastructure service capable V2X UE in awireless network. In an example embodiment, the message for a new dialogestablishment or a standalone message may employ one or more IMScommunication identifiers (ICSI) for capabilities such as for beingvehicle-to-network service capable V2X UE in a wireless network.

In an example embodiment, the message for a new dialog establishment ora standalone message may employ one or more IMS communicationidentifiers (ICSI) for capabilities such as for being pedestrian,vehicle, infrastructure, vehicle-to-vehicle service,vehicle-to-pedestrian service, vehicle-to-infrastructure service, and/orvehicle-to-network service capable V2X UE in a wireless network. In anexample embodiment, the message for a new dialog establishment or astandalone message may employ one or more IMS communication identifiers(ICSI) for capabilities such as for being emergency V2X UE capable in awireless network. In an example embodiment, the message for a new dialogestablishment or a standalone message may employ one or more IMScommunication identifiers (ICSI) for capabilities such as for beingemergency pedestrian capable V2X UE in a wireless network.

In an example embodiment, the message for a new dialog establishment ora standalone message may employ one or more IMS communicationidentifiers (ICSI) for capabilities such as for being emergency vehiclecapable V2X UE in a wireless network. In an example embodiment, themessage for a new dialog establishment or a standalone message mayemploy one or more IMS communication identifiers (ICSI) for capabilitiessuch as for being emergency infrastructure capable V2X UE in a wirelessnetwork. In an example embodiment, the message for a new dialogestablishment or a standalone message may employ one or more IMScommunication identifiers (ICSI) for capabilities such as for beingemergency vehicle-to-pedestrian service capable V2X UE in a wirelessnetwork. In an example embodiment, the message for a new dialogestablishment or a standalone message may employ one or more IMScommunication identifiers (ICSI) for capabilities such as for beingemergency vehicle-to-vehicle service capable V2X UE in a wirelessnetwork. In an example embodiment, the message for a new dialogestablishment or a standalone message may employ one or more IMScommunication identifiers (ICSI) for capabilities such as for beingemergency vehicle-to-infrastructure service capable V2X UE in a wirelessnetwork. In an example embodiment, the message for a new dialogestablishment or standalone message may employ one or more IMScommunication identifiers (ICSI) for capabilities such as for beingemergency vehicle-to-network service capable V2X UE in a wirelessnetwork.

In an example embodiment, the message for a new dialog establishment ora standalone message may employ one or more IMS communicationidentifiers (ICSI) for capabilities such as for being emergencypedestrian, emergency vehicle, emergency infrastructure, emergencyvehicle-to-vehicle service, emergency vehicle-to-pedestrian service,emergency vehicle-to-infrastructure service, and/or emergencyvehicle-to-network service capable V2X UE in a wireless network.

In an example embodiment, the message for a new dialog establishment ora standalone message may employ one or more IMS application referenceidentifiers (IARI) for capabilities such as for being V2X UE capable ina wireless network. In an example embodiment, the message for a newdialog establishment or a standalone message may employ one or more IMSapplication reference identifiers (IARI) for capabilities such as forbeing pedestrian capable V2X UE in a wireless network. In an exampleembodiment, the message for a new dialog establishment or a standalonemessage may employ one or more IMS application reference identifiers(IARI) for capabilities such as for being vehicle capable V2X UE in awireless network. In an example embodiment, the message for a new dialogestablishment or a standalone message may employ one or more IMSapplication reference identifiers (IARI) for capabilities such as forbeing infrastructure capable V2X UE in a wireless network. In an exampleembodiment, the message for a new dialog establishment or a standalonemessage may employ one or more IMS application reference identifiers(IARI) for capabilities such as for being vehicle-to-pedestrianapplication capable V2X UE in a wireless network. In an exampleembodiment, the message for a new dialog establishment or a standalonemessage may employ one or more IMS application reference identifiers(IARI) for capabilities such as for being vehicle-to-vehicle applicationcapable V2X UE in a wireless network. In an example embodiment, themessage for a new dialog establishment or a standalone message mayemploy one or more IMS application reference identifiers (IARI) forcapabilities such as for being vehicle-to-infrastructure applicationcapable V2X UE in a wireless network. In an example embodiment, themessage for a new dialog establishment or a standalone message mayemploy one or more IMS application reference identifiers (IARI) forcapabilities such as for being vehicle-to-network application capableV2X UE in a wireless network.

In an example embodiment, the message for a new dialog establishment ora standalone message may employ one or more IMS application referenceidentifiers (IARI) for capabilities such as for being pedestrian,vehicle, infrastructure, vehicle-to-vehicle application,vehicle-to-pedestrian application, vehicle-to-infrastructureapplication, and/or vehicle-to-network application capable V2X UE in awireless network.

In an example embodiment, the message for a new dialog establishment ora standalone message may employ one or more IMS application referenceidentifiers (IARI) for capabilities such as for being emergency V2X UEcapable in a wireless network. In an example embodiment, the message fora new dialog establishment or a standalone message may employ one ormore IMS application reference identifiers (IARI) for capabilities suchas for being emergency pedestrian capable V2X UE in a wireless network.In an example embodiment, the message for a new dialog establishment ora standalone message may employ one or more IMS application referenceidentifiers (IARI) for capabilities such as for being emergency vehiclecapable V2X UE in a wireless network. In an example embodiment, themessage for a new dialog establishment or a standalone message mayemploy one or more IMS application reference identifiers (IARI) forcapabilities such as for being emergency infrastructure capable V2X UEin a wireless network. In an example embodiment, the message for a newdialog establishment or a standalone message may employ one or more IMSapplication reference identifiers (IARI) for capabilities such as forbeing emergency vehicle-to-pedestrian application capable V2X UE in awireless network.

In an example embodiment, the message for a new dialog establishment ora standalone message may employ one or more IMS application referenceidentifiers (IARI) for capabilities such as for being emergencyvehicle-to-vehicle application capable V2X UE in a wireless network. Inan example embodiment, the message for a new dialog establishment or astandalone message may employ one or more IMS application referenceidentifiers (IARI) for capabilities such as for being emergencyvehicle-to-infrastructure application capable V2X UE in a wirelessnetwork. In an example embodiment, the message for a new dialogestablishment or a standalone message may employ one or more IMSapplication reference identifiers (IARI) for capabilities such as forbeing emergency vehicle-to-network application capable V2X UE in awireless network.

In an example embodiment, the message for a new dialog establishment ora standalone message may employ one or more IMS application referenceidentifiers (IARI) for capabilities such as for being emergencypedestrian, emergency vehicle, emergency infrastructure, emergencyvehicle-to-vehicle application, emergency vehicle-to-pedestrianapplication, emergency vehicle-to-infrastructure application, and/oremergency vehicle-to-network application capable V2X UE in a wirelessnetwork.

In an example embodiment, a V2X UE may proxy one or many other V2X UEsfor ICSI registration and/or IARI registration to the IMS network withno modification to the message for a new dialog establishment or astandalone message. In an example embodiment, a V2X UE may proxy one ormany other V2X UEs for ICSI registration and/or IARI registration to theIMS network with modification to the header of the message for a newdialog establishment or a standalone message. In an example embodiment,a V2X UE may proxy one or many other V2X UEs for ICSI registrationand/or IARI registration to the IMS network with modification to thebody of the message for a new dialog establishment or a standalonemessage. In an example embodiment, a V2X UE may proxy one or many otherV2X UEs for ICSI registration and/or IARI registration to the IMSnetwork with modification to the header and the body of the message fora new dialog establishment or a standalone message. Other combinationfor creating feature tags for service and application identifiers forV2X may be implemented.

The flow diagram in the example embodiment in FIG. 18 shows a V2X UEsends a request to V2X AS. FIG. 18 shows that V2X UE may send a requestfor a service or send an information to the network which may compriseV2X related ICSI and IARI in the Contact header field. TheAccept-Contact header field may also comprise the V2X related ICSI andIARI which may indicate that the V2X service or the V2X applicationwhich may be required for the V2X service, I-CSCF may get help HSS tolocate the suitable S-CSCF to process the V2X UE request, S-CSCF mayforward the request to the V2X AS which may analyze the request from theV2X UE, and V2X AS may send an appropriate response to V2X UE.

According to an example embodiment, a method may comprise registering,by a wireless device, one or more IMS communication service identifiers(ICSIs) of V2X in a wireless network, wherein one of the one or moreICSIs indicates at least V2X capability of the wireless device.According to an example embodiment, a method may comprise registering,by a wireless device, one or more IMS communication service identifiers(ICSIs) of V2X in a wireless network, wherein one of the one or moreICSIs indicates at least emergency V2X capability of the wirelessdevice.

According to an example embodiment, a method may comprise registering,by a wireless device, one or more IMS communication service identifiers(ICSIs) of V2X in a wireless network, wherein one of the one or moreICSIs indicates at least V2X capability of the wireless device.According to an example embodiment, a method may comprise registering,by a wireless device, one or more IMS communication service identifiers(ICSIs) of V2X in a wireless network, wherein one of the one or moreICSIs indicates at least V2X capability of the wireless device.

According to an example embodiment, a method may comprise registering,by a wireless device, one or more IMS communication service identifiers(ICSIs) of V2X in a wireless network, wherein one of the one or moreICSIs indicates at least vehicle capability of the wireless device.According to an example embodiment, a method may comprise registering,by a wireless device, one or more IMS communication service identifiers(ICSIs) of V2X in a wireless network, wherein one of the one or moreICSIs indicates at least emergency vehicle capability of the wirelessdevice.

According to an example embodiment, a method may comprise, registering,by a wireless device, one or more IMS communication service identifiers(ICSIs) of V2X in a wireless network, wherein one of the one or moreICSIs indicates at least pedestrian capability of the wireless device.According to an example embodiment, a method may comprise, registering,by a wireless device, one or more IMS communication service identifiers(ICSIs) of V2X in a wireless network, wherein one of the one or moreICSIs indicates at least emergency pedestrian capability of the wirelessdevice.

According to an example embodiment, a method may comprise, registering,by a wireless device, one or more IMS communication service identifiers(ICSIs) of V2X in a wireless network, wherein one of the one or moreICSIs indicates at least infrastructure capability of the wirelessdevice. According to an example embodiment, a method may comprise,registering, by a wireless device, one or more IMS communication serviceidentifiers (ICSIs) of V2X in a wireless network, wherein one of the oneor more ICSIs indicates at least emergency infrastructure capability ofthe wireless device.

According to an example embodiment, a method may comprise registering,by a wireless device, one or more IMS communication service identifiers(ICSIs) of V2X in a wireless network, wherein one of the one or moreICSIs indicates at least vehicle-to-vehicle service capability of thewireless device. According to an example embodiment, a method maycomprise, registering, by a wireless device, one or more IMScommunication service identifiers (ICSIs) of V2X in a wireless network,wherein one of the one or more ICSIs indicates at least emergencyvehicle-to-vehicle service capability of the wireless device.

According to an example embodiment, a method may comprise registering,by a wireless device, one or more IMS communication service identifiers(ICSIs) of V2X in a wireless network, wherein one of the one or moreICSIs indicates at least vehicle-to-pedestrian service capability of thewireless device. According to an example embodiment, a method maycomprise, registering, by a wireless device, one or more IMScommunication service identifiers (ICSIs) of V2X in a wireless network,wherein one of the one or more ICSIs indicates at least emergencyvehicle-to-pedestrian service capability of the wireless device.

According to an example embodiment, a method may comprise registering,by a wireless device, one or more IMS communication service identifiers(ICSIs) of V2X in a wireless network, wherein one of the one or moreICSIs indicates at least vehicle-to-infrastructure service capability ofthe wireless device. According to an example embodiment, a method maycomprise registering, by a wireless device, one or more IMScommunication service identifiers (ICSIs) of V2X in a wireless network,wherein one of the one or more ICSIs indicates at least emergencyvehicle-to-infrastructure service capability of the wireless device.

According to an example embodiment, a method may comprise registering,by a wireless device, one or more IMS communication service identifiers(ICSIs) of V2X in a wireless network, wherein one of the one or moreICSIs indicates at least vehicle-to-network service capability of thewireless device. According to an example embodiment, a method maycomprise registering, by a wireless device, one or more IMScommunication service identifiers (ICSIs) of V2X in a wireless network,wherein one of the one or more ICSIs indicates at least emergencyvehicle-to-network service capability of the wireless device.

According to an example embodiment, a method may comprise registering,by a wireless device, one or more IMS communication service identifiers(ICSIs) of V2X in a wireless network, wherein the one or more ICSIsindicate a combination of at least two of vehicle, pedestrian,infrastructure, vehicle-to-vehicle service, vehicle-to-pedestrianservice, vehicle-to infrastructure service, and/or vehicle-to-networkservice capabilities of the wireless device.

According to an example embodiment, a method may comprise registering,by a wireless device, one or more IMS communication service identifiers(ICSIs) of V2X in a wireless network, wherein the one or more ICSIsindicate a combination of at least two of emergency vehicle, emergencypedestrian, emergency infrastructure, emergency vehicle-to-vehicleservice, emergency vehicle-to-pedestrian service, emergency vehicle-toinfrastructure service, and/or emergency vehicle-to-network servicecapabilities of the wireless device.

According to an example embodiment, a method may comprise registering,by a wireless device, one or more IMS communication service identifiers(ICSIs) of V2X in a wireless network, wherein one of the one or moreICSIs indicates at least V2X capability of the wireless device, furtherregistering one or more IMS application reference identifiers (IARIs),wherein one of the one or more IARIs indicates at least one of vehiclecapability of the wireless device. The method may further register oneor more IMS application reference identifiers (IARIs), wherein one ofthe one or more IARIs indicates at least one of emergency vehiclecapability of the wireless device.

According to an example embodiment, a method may comprise registering,by a wireless device, one or more IMS communication service identifiers(ICSIs) of V2X in a wireless network, wherein one of the one or moreICSIs indicates at least V2X capability of the wireless device, furtherregistering one or more IMS application reference identifiers (IARIs),wherein one of the one or more IARIs indicates at least one ofpedestrian capability of the wireless device.

According to an example embodiment, a method may comprise registering,by a wireless device, one or more IMS communication service identifiers(ICSIs) of V2X in a wireless network, wherein one of the one or moreICSIs indicates at least V2X capability of the wireless device, furtherregistering one or more IMS application reference identifiers (IARIs),wherein one of the one or more IARIs indicates at least one of emergencypedestrian capability of the wireless device.

According to an example embodiment, a method may comprise registering,by a wireless device, one or more IMS communication service identifiers(ICSIs) of V2X in a wireless network, wherein one of the one or moreICSIs indicates at least V2X capability of the wireless device, furtherregistering one or more IMS application reference identifiers (IARIs),wherein one of the one or more IARIs indicates at least one ofinfrastructure capability of the wireless device.

According to an example embodiment, a method may comprise registering,by a wireless device, one or more IMS communication service identifiers(ICSIs) of V2X in a wireless network, wherein one of the one or moreICSIs indicates at least V2X capability of the wireless device, furtherregistering one or more IMS application reference identifiers (IARIs),wherein one of the one or more IARIs indicates at least one of emergencyinfrastructure capability of the wireless device.

According to an example embodiment, a method may comprise registering,by a wireless device, one or more IMS application reference identifiers(IARIs) of V2X in a wireless network, wherein one of the one or moreIARIs indicates at least one of V2X capability of the wireless device.According to an example embodiment, a method may comprise registering,by a wireless device, one or more IMS application reference identifiers(IARIs) of V2X in a wireless network, wherein one of the one or moreIARIs indicates at least one of emergency V2X capability of the wirelessdevice.

According to an example embodiment, a method may comprise registering,by a wireless device, one or more IMS application reference identifiers(IARIs) of V2X in a wireless network wherein one of the one or moreIARIs indicates at least one of vehicle capability of the wirelessdevice. According to an example embodiment, a method may compriseregistering, by a wireless device, one or more IMS application referenceidentifiers (IARIs) of V2X in a wireless network, wherein one of the oneor more IARIs indicates at least one of emergency vehicle capability ofthe wireless device.

According to an example embodiment, a method may comprise registering,by a wireless device, one or more IMS application reference identifiers(IARIs) of V2X in a wireless network, wherein one of the one or moreIARIs indicates at least one of pedestrian capability of the wirelessdevice. According to an example embodiment, a method may compriseregistering, by a wireless device, one or more IMS application referenceidentifiers (IARIs) of V2X in a wireless network, wherein one of the oneor more IARIs indicates at least one of emergency pedestrian capabilityof the wireless device.

According to an example embodiment, a method may comprise registering,by a wireless device, one or more IMS application reference identifiers(IARIs) of V2X in a wireless network, wherein one of the one or moreIARIs indicates at least one of infrastructure capability of thewireless device. According to an example embodiment, a method maycomprise registering, by a wireless device, one or more IMS applicationreference identifiers (IARIs) of V2X in a wireless network, wherein oneof the one or more IARIs indicates at least one of emergencyinfrastructure capability of the wireless device.

According to an example embodiment, a method may comprise registering,by a wireless device, one or more IMS application reference identifiers(IARIs) of V2X in a wireless network, wherein one of the one or moreIARIs indicates at least one of vehicle-to-vehicle applicationcapability of the wireless device. According to an example embodiment, amethod may comprise registering, by a wireless device, one or more IMSapplication reference identifiers (IARIs) of V2X in a wireless network,wherein one of the one or more IARIs indicates at least one of emergencyvehicle-to-vehicle application capability of the wireless device.

According to an example embodiment, a method may comprise registering,by a wireless device, one or more IMS application reference identifiers(IARIs) of V2X in a wireless network wherein one of the one or moreIARIs indicates at least one of vehicle-to-pedestrian applicationcapability of the wireless device. According to an example embodiment, amethod may comprise registering, by a wireless device, one or more IMSapplication reference identifiers (IARIs) of V2X in a wireless networkwherein one of the one or more IARIs indicates at least one of emergencyvehicle-to-pedestrian application capability of the wireless device.

According to an example embodiment, a method may comprise registering,by a wireless device, one or more IMS application reference identifiers(IARIs) of V2X in a wireless network wherein one of the one or moreIARIs indicates at least one of vehicle-to-infrastructure applicationcapability of the wireless device. According to an example embodiment, amethod may comprise registering, by a wireless device, one or more IMSapplication reference identifiers (IARIs) of V2X in a wireless network,wherein one of the one or more IARIs indicates at least one of emergencyvehicle-to-infrastructure application capability of the wireless device.

According to an example embodiment, a method may comprise registering,by a wireless device, one or more IMS application reference identifiers(IARIs) of V2X in a wireless network wherein one of the one or moreIARIs indicates at least one of vehicle-to-network applicationcapability of the wireless device. According to an example embodiment, amethod may comprise registering, by a wireless device, one or more IMSapplication reference identifiers (IARIs) of V2X in a wireless network,wherein one of the one or more IARIs indicates at least one of emergencyvehicle-to-network application capability of the wireless device.

According to an example embodiment, a method may comprise registering,by a wireless device, one or more IMS application reference identifiers(IARIs) of push-to-talk in a wireless network wherein the one or moreIARIs indicate a combination of at least two of vehicle, pedestrian,infrastructure, vehicle-to-vehicle application, vehicle-to-pedestrianapplication, vehicle-to infrastructure application, and/or vehicle-tonetwork application capabilities of the wireless device. According to anexample embodiment, a method may comprise registering, by a wirelessdevice, one or more IMS application reference identifiers (IARIs) ofpush-to-talk in a wireless network wherein the one or more IARIsindicate a combination of at least two of vehicle, pedestrian,infrastructure, vehicle-to-vehicle application, vehicle-to-pedestrianapplication, vehicle-to infrastructure application, and/or vehicle-tonetwork application capabilities of the wireless device.

According to an example embodiment, a method may comprise registering,by a wireless device, one or more IMS communication service identifiers(ICSIs) and one or more IMS application reference identifiers (IARIs) ofpush-to-talk in a wireless network, wherein one of the one or more ICSIsand one of the one or more IARIs indicates at least one of emergencyvehicle, emergency pedestrian, emergency infrastructure, emergencyvehicle-to-vehicle, emergency vehicle-to-pedestrian, emergencyvehicle-to-infrastructure, and/or emergency vehicle-to-networkcapabilities of the V2X device.

According to an example embodiment, a method may comprise performing anew dialog establishment or a standalone transaction, by a wirelessdevice, one or more IMS communication service identifiers (ICSIs) of V2Xin a wireless network, wherein one of the one or more ICSIs indicates atleast V2X capability of the wireless device. According to an exampleembodiment, a method may comprise performing a new dialog establishmentor a standalone transaction, by a wireless device, one or more IMScommunication service identifiers (ICSIs) of V2X in a wireless network,wherein one of the one or more ICSIs indicates at least vehiclecapability of the wireless device.

According to an example embodiment, a method may comprise performing anew dialog establishment or a standalone transaction, by a wirelessdevice, one or more IMS communication service identifiers (ICSIs) of V2Xin a wireless network, wherein one of the one or more ICSIs indicates atleast pedestrian capability of the wireless device. According to anexample embodiment, a method may comprise performing a new dialogestablishment or a standalone transaction, by a wireless device, one ormore IMS communication service identifiers (ICSIs) of V2X in a wirelessnetwork, wherein one of the one or more ICSIs indicates at leastinfrastructure capability of the wireless device.

According to an example embodiment, a method may comprise performing anew dialog establishment or a standalone transaction, by a wirelessdevice, one or more IMS communication service identifiers (ICSIs) of V2Xin a wireless network wherein the one or more ICSIs indicate acombination of at least two of vehicle, pedestrian, and infrastructurecapabilities of the wireless device.

According to an example embodiment, a method may comprise performing anew dialog establishment or a standalone transaction, by a wirelessdevice, one or more IMS communication service identifiers (ICSIs) of V2Xin a wireless network, wherein one of the one or more ICSIs indicates atleast V2X capability of the wireless device, further adding for a newdialog establishment or a standalone transaction one or more IMSapplication reference identifiers (IARIs), wherein one of the one ormore IARIs indicates at least one of vehicle capability of the wirelessdevice.

According to an example embodiment, a method may comprise performing anew dialog establishment or a standalone transaction, by a wirelessdevice, one or more IMS communication service identifiers (ICSIs) of V2Xin a wireless network, wherein one of the one or more ICSIs indicates atleast V2X capability of the wireless device, further adding for a newdialog establishment or a standalone transaction one or more IMSapplication reference identifiers (IARIs), wherein one of the one ormore IARIs indicates at least one of pedestrian capability of thewireless device.

According to an example embodiment, a method may comprise performing anew dialog establishment or a standalone transaction, by a wirelessdevice, one or more IMS communication service identifiers (ICSIs) of V2Xin a wireless network, wherein one of the one or more ICSIs indicates atleast V2X capability of the wireless device, further adding for a newdialog establishment or a standalone transaction one or more IMSapplication reference identifiers (IARIs), wherein one of the one ormore IARIs indicates at least one of infrastructure capability of thewireless device.

According to an example embodiment, a method may comprise performing anew dialog establishment or a standalone transaction, by a wirelessdevice, one or more IMS communication service identifiers (ICSIs) of V2Xin a wireless network, wherein one of the one or more ICSIs indicates atleast V2X capability of the wireless device, further adding for a newdialog establishment or a standalone transaction one or more IMSapplication reference identifiers (IARIs), wherein one of the one ormore IARIs indicates at least one of vehicle-to-vehicle capability ofthe wireless device.

According to an example embodiment, a method may comprise performing anew dialog establishment or a standalone transaction, by a wirelessdevice, one or more IMS communication service identifiers (ICSIs) of V2Xin a wireless network, wherein one of the one or more ICSIs indicates atleast V2X capability of the wireless device, further adding for a newdialog establishment or a standalone transaction one or more IMSapplication reference identifiers (IARIs), wherein one of the one ormore IARIs indicates at least one of vehicle-to-network capability ofthe wireless device.

According to an example embodiment, a method may comprise performing anew dialog establishment or a standalone transaction, by a wirelessdevice, one or more IMS communication service identifiers (ICSIs) of V2Xin a wireless network, wherein one of the one or more ICSIs indicates atleast V2X capability of the wireless device, further adding for a newdialog establishment or a standalone transaction one or more IMSapplication reference identifiers (IARIs), wherein one of the one ormore IARIs indicates at least one of vehicle-to-pedestrian capability ofthe wireless device.

According to an example embodiment, a method may comprise performing anew dialog establishment or a standalone transaction, by a wirelessdevice, one or more IMS communication service identifiers (ICSIs) of V2Xin a wireless network, wherein one of the one or more ICSIs indicates atleast V2X capability of the wireless device, further adding for a newdialog establishment or a standalone transaction one or more IMSapplication reference identifiers (IARIs), wherein one of the one ormore IARIs indicates at least one of vehicle-to-infrastructurecapability of the wireless device.

According to an example embodiment, a method may comprise performing anew dialog establishment or a standalone transaction, by a wirelessdevice, one or more IMS application reference identifiers (IARIs) of V2Xin a wireless network wherein one of the one or more IARIs indicates atleast one of V2X capability of the wireless device.

According to an example embodiment, a method may comprise performing anew dialog establishment or a standalone transaction, by a wirelessdevice, one or more IMS application reference identifiers (IARIs) of V2Xin a wireless network, wherein one of the one or more IARIs indicates atleast one of vehicle capability of the wireless device. According to anexample embodiment, a method may comprise performing a new dialogestablishment or a standalone transaction, by a wireless device, one ormore IMS application reference identifiers (IARIs) of V2X in a wirelessnetwork wherein one of the one or more IARIs indicates at least one ofpedestrian capability of the wireless device.

According to an example embodiment, a method may comprise performing anew dialog establishment or a standalone transaction, by a wirelessdevice, one or more IMS application reference identifiers (IARIs) of V2Xin a wireless network, wherein one of the one or more IARIs indicates atleast one of infrastructure capability of the wireless device. Accordingto an example embodiment, a method may comprise performing a new dialogestablishment or a standalone transaction, by a wireless device, one ormore IMS application reference identifiers (IARIs) of V2X in a wirelessnetwork, wherein one of the one or more IARIs indicates at least one ofvehicle-to-vehicle capability of the wireless device.

According to an example embodiment, a method may comprise performing anew dialog establishment or a standalone transaction, by a wirelessdevice, one or more IMS application reference identifiers (IARIs) of V2Xin a wireless network wherein one of the one or more IARIs indicates atleast one of vehicle-to-network capability of the wireless device.According to an example embodiment, a method may comprise performing anew dialog establishment or a standalone transaction, by a wirelessdevice, one or more IMS application reference identifiers (IARIs) of V2Xin a wireless network, wherein one of the one or more IARIs indicates atleast one of vehicle-to-infrastructure capability of the wirelessdevice.

According to an example embodiment, a method may comprise performing anew dialog establishment or a standalone transaction, by a wirelessdevice, one or more IMS application reference identifiers (IARIs) of V2Xin a wireless network, wherein one of the one or more IARIs indicates atleast one of vehicle-to-network capability of the wireless device.According to an example embodiment, a method may comprise performing anew dialog establishment or a standalone transaction, by a wirelessdevice, one or more IMS application reference identifiers (IARIs) ofpush-to-talk in a wireless network. According to an embodiment, a methodmay comprise performing a new dialog establishment or a standalonetransaction, by a wireless device, one or more IMS communication serviceidentifiers (ICSIs) of V2X in a wireless network, wherein one of the oneor more ICSIs indicates at least V2X capability of the wireless device.

According to an embodiment, a method may comprise performing a newdialog establishment or a standalone transaction, by a wireless device,one or more IMS communication service identifiers (ICSIs) of V2X in awireless network, wherein one of the one or more ICSIs indicates atleast emergency vehicle capability of the wireless device. According toan embodiment, a method may comprise performing a new dialogestablishment or a standalone transaction, by a wireless device, one ormore IMS communication service identifiers (ICSIs) of V2X in a wirelessnetwork, wherein one of the one or more ICSIs indicates at leastemergency pedestrian capability of the wireless device.

According to an example embodiment, a method may comprise performing anew dialog establishment or a standalone transaction, by a wirelessdevice, one or more IMS communication service identifiers (ICSIs) of V2Xin a wireless network, wherein one of the one or more ICSIs indicates atleast emergency infrastructure capability of the wireless device.According to an example embodiment, a method may comprise performing anew dialog establishment or a standalone transaction, by a wirelessdevice, one or more IMS communication service identifiers (ICSIs) of V2Xin a wireless network, wherein the one or more ICSIs indicate acombination of at least two of emergency vehicle, emergency pedestrian,and emergency infrastructure capabilities of the wireless device.

According to an example embodiment, a method may comprise performing anew dialog establishment or a standalone transaction, by a wirelessdevice, one or more IMS application reference identifiers (IARIs) of V2Xin a wireless network, wherein one of the one or more IARIs indicates atleast one of vehicle capability of the wireless device, further addingfor a new dialog establishment or a standalone transaction one or moreIMS application reference identifiers (IARIs), wherein one of the one ormore IARIs indicates at least one of emergency vehicle capability of thewireless device.

According to an example embodiment, a method may comprise performing anew dialog establishment or a standalone transaction, by a wirelessdevice, one or more IMS application reference identifiers (IARIs) of V2Xin a wireless network, wherein one of the one or more IARIs indicates atleast one of vehicle capability of the wireless device, further addingfor a new dialog establishment or a standalone transaction one or moreIMS application reference identifiers (IARIs), wherein one of the one ormore IARIs indicates at least one of emergency pedestrian capability ofthe wireless device.

According to an example embodiment, a method may comprise performing anew dialog establishment or a standalone transaction, by a wirelessdevice, one or more IMS application reference identifiers (IARIs) of V2Xin a wireless network, wherein one of the one or more IARIs indicates atleast one of vehicle capability of the wireless device, further addingfor a new dialog establishment or a standalone transaction one or moreIMS application reference identifiers (IARIs), wherein one of the one ormore IARIs indicates at least one of emergency infrastructure capabilityof the wireless device.

According to an example embodiment, a method may comprise performing anew dialog establishment or a standalone transaction, by a wirelessdevice, one or more IMS application reference identifiers (IARIs) of V2Xin a wireless network, wherein one of the one or more IARIs indicates atleast one of vehicle capability of the wireless device, further addingfor a new dialog establishment or a standalone transaction one or moreIMS application reference identifiers (IARIs), wherein one of the one ormore IARIs indicates at least one of emergency vehicle-to-vehiclecapability of the wireless device.

According to an example embodiment, a method may comprise performing anew dialog establishment or a standalone transaction, by a wirelessdevice, one or more IMS application reference identifiers (IARIs) of V2Xin a wireless network, wherein one of the one or more IARIs indicates atleast one of vehicle capability of the wireless device, further addingfor a new dialog establishment or a standalone transaction one or moreIMS application reference identifiers (IARIs), wherein one of the one ormore IARIs indicates at least one of emergency vehicle-to-networkcapability of the wireless device.

According to an example embodiment, a method may comprise performing anew dialog establishment or a standalone transaction, by a wirelessdevice, one or more IMS application reference identifiers (IARIs) of V2Xin a wireless network, wherein one of the one or more IARIs indicates atleast one of vehicle capability of the wireless device, further addingfor a new dialog establishment or a standalone transaction one or moreIMS application reference identifiers (IARIs), wherein one of the one ormore IARIs indicates at least one of emergency vehicle-to-pedestriancapability of the wireless device.

According to an example embodiment, a method may comprise performing anew dialog establishment or a standalone transaction, by a wirelessdevice, one or more IMS application reference identifiers (IARIs) of V2Xin a wireless network, wherein one of the one or more IARIs indicates atleast one of vehicle capability of the wireless device, further addingfor a new dialog establishment or a standalone transaction one or moreIMS application reference identifiers (IARIs), wherein one of the one ormore IARIs indicates at least one of emergency vehicle-to-infrastructurecapability of the wireless device.

According to an example embodiment, a method may comprise performing anew dialog establishment or a standalone transaction, by a wirelessdevice, one or more IMS application reference identifiers (IARIs) of V2Xin a wireless network wherein one of the one or more IARIs indicates atleast one of emergency V2X capability of the wireless device. Accordingto an example embodiment, a method may comprise performing a new dialogestablishment or a standalone transaction, by a wireless device, one ormore IMS application reference identifiers (IARIs) of V2X in a wirelessnetwork wherein one of the one or more IARIs indicates at least one ofemergency vehicle capability of the wireless device.

According to an example embodiment, a method may comprise performing anew dialog establishment or a standalone transaction, by a wirelessdevice, one or more IMS application reference identifiers (IARIs) of V2Xin a wireless network wherein one of the one or more IARIs indicates atleast one of emergency pedestrian capability of the wireless device.According to an example embodiment, a method may comprise performing anew dialog establishment or a standalone transaction, by a wirelessdevice, one or more IMS application reference identifiers (IARIs) of V2Xin a wireless network wherein one of the one or more IARIs indicates atleast one of emergency infrastructure capability of the wireless device.

According to an example embodiment, a method may comprise performing anew dialog establishment or a standalone transaction, by a wirelessdevice, one or more IMS application reference identifiers (IARIs) of V2Xin a wireless network, wherein one of the one or more IARIs indicates atleast one of emergency vehicle-to-vehicle capability of the wirelessdevice. According to an example embodiment, a method may compriseperforming a new dialog establishment or a standalone transaction, by awireless device, one or more IMS application reference identifiers(IARIs) of V2X in a wireless network; wherein one of the one or moreIARIs indicates at least one of emergency vehicle-to-network capabilityof the wireless device.

According to an example embodiment, a method may comprise performing anew dialog establishment or a standalone transaction, by a wirelessdevice, one or more IMS application reference identifiers (IARIs) of V2Xin a wireless network wherein one of the one or more IARIs indicates atleast one of emergency vehicle-to-infrastructure capability of thewireless device. According to an example embodiment, a method maycomprise performing a new dialog establishment or a standalonetransaction, by a wireless device, one or more IMS application referenceidentifiers (IARIs) of V2X in a wireless network wherein one of the oneor more IARIs indicates at least one of emergency vehicle-to-networkcapability of the wireless device.

According to an example embodiment, a method may comprise performing anew dialog establishment or a standalone transaction, by a wirelessdevice, one or more IMS application reference identifiers (IARIs) ofpush-to-talk in a wireless network wherein the one or more IARIsindicate a combination of at least two of emergency vehicle, emergencypedestrian, emergency infrastructure, emergency vehicle-to-vehicle,emergency vehicle-to-pedestrian, emergency vehicle-to-network, and/oremergency vehicle-to-infrastructure capabilities of the wireless device.

According to an example embodiment, a method may comprise performing anew dialog establishment or a standalone transaction, by a wirelessdevice, one or more IMS communication service identifiers (ICSIs) andone or more IMS application reference identifiers (IARIs) ofpush-to-talk in a wireless network wherein one of the one or more ICSIsand one of the one or more IARIs indicates at least one of emergencyvehicle, emergency pedestrian, emergency infrastructure, emergencyvehicle-to-vehicle, emergency vehicle-to-pedestrian, emergencyvehicle-to-network, and/or emergency vehicle-to-infrastructurecapabilities of the V2X device.

In an example embodiment, in FIG. 19, V2X may be considered as groupcommunication system enabler which may employ E-UTRAN broadcastmulticast bearer for delivering the media to the end users. In FIG. 19,MBMS-GW=multimedia broadcast multicast service gateway, BM-SC=broadcastmulticast service center, PCRF=policy charging rules function.

In one example embodiment, VMB2 reference point may provide ability forV2X AS to request allocation of temporary mobile group identifiers(TMGIs) from BM-SC. In one example embodiment, VMB2 reference point mayprovide ability for V2X AS to request deallocation of TMGIs from BM-SC.In one example embodiment, VMB2 may provide the ability for BM-SC toreport the status of MBMS bearer to V2X AS. In one example embodiment,VC1 reference point may provide ability for V2X AS to send theinformation about connectivity to the broadcast bearer to the V2X UE. Inone example embodiment, the VC1 reference point may provide the abilityfor V2X UE to send information about broadcast multicast coverage to theV2X AS.

In one example embodiment, the reference point VC1 may employ SIP forcommunication between the V2X UE and the V2X AS. The dialogs, newdialogs, and the standalone transactions between the V2X UE and the V2XAS may comprise requests and responses which may employ one or more IMScommunication service identifiers (ICSIs) of V2X and ICSIs ofbroadcast/multicast V2X service. One of the one or more ICSIs mayindicate at least one of pedestrian, vehicle infrastructure,vehicle-to-vehicle, vehicle-to-pedestrian, vehicle-to-network, and/orvehicle-to-infrastructure capabilities of the V2X service. ICSI may bein the form of a media feature tag. A feature tag may indicate the V2Xservice. For example, a specific feature tag, such as3gpp-service.ims.icsi.v2x may indicate the V2X service or3gpp-service.ims.icsi.v2n may indicate the vehicle-to-networkcapability. A feature tag may indicate one or more capability of the V2Xservice. For example, a specific feature tag, such as3gpp-service.ims.icsi.v2x.rsu may indicate infrastructure capability ofthe V2X service. A feature tag may indicate the broadcast/multicastservice. For example, a specific feature tag, such as3gpp-service.ims.icsi.v2x.multicast may indicate the multicast/broadcastV2X service or 3gpp-service.ims.icsi.v2n.multicast may indicate themulticast/broadcast vehicle-to-network service. These are examples,other features tag names may be used. One or more ICSI may indicate acombination of at least two of pedestrian, vehicle, infrastructure,vehicle-to-vehicle, vehicle-to-pedestrian, vehicle-to-network, and/orvehicle-to-infrastructure capabilities of the V2X service. For example,a feature tag 3gpp-service.ims.icsi.v2x, may indicate capability forvehicle, pedestrian, infrastructure, vehicle-to-vehicle,vehicle-to-pedestrian, vehicle-to-network, and/orvehicle-to-infrastructure. In an example, a feature tag3gpp-service.ims.icsi.v2x.emergency, may indicate capability foremergency vehicle, emergency pedestrian, emergency infrastructure,emergency vehicle-to-vehicle, emergency vehicle-to-pedestrian, emergencyvehicle-to-network, and/or emergency vehicle-to-infrastructure.

In an example embodiment, the message for the dialog, new dialog, andthe standalone transaction between V2X UE and V2X AS over VC1 referencepoint may further employ one or more IMS application referenceidentifiers (IARIs). One of the one or more IARIs may indicate at leastone of pedestrian, vehicle, infrastructure, vehicle-to-vehicle,vehicle-to-pedestrian, vehicle-to-network, and/orvehicle-to-infrastructure capabilities of the V2X application. IARI maybe in the form of a media feature tag. A feature tag may indicate theV2X application. For example, a specific feature tag, such as3gpp-application.ims.iari.v2x may indicate the V2X application or3gpp-application.ims.iari.ve2 may indicate the vehicle-to-networkapplication. A feature tag may indicate the broadcast/multicastapplication. For example, a specific feature tag, such as3gpp-application.ims.iari.v2x.multicast may indicate themulticast/broadcast V2X application or3gpp-application.ims.iari.v2n.multicast may indicate themulticast/broadcast vehicle-to-network application. A feature tag mayindicate one or more capability of the V2X application. For example, aspecific feature tag, such as 3gpp-application.ims.iari.v2x.vehicle mayindicate V2X UE with vehicle capability or3gpp-application.ims.iari.v2x.vehicle-to-vehicle may indicate V2X UEwith vehicle-to-vehicle capability. These are examples and otherfeatures tag names may be used. One or more IARI may indicate acombination of at least two of pedestrian, vehicle, infrastructure,vehicle-to-vehicle, vehicle-to-pedestrian, vehicle-to-network, and/orvehicle-to-infrastructure capabilities of the V2X application. Forexample, a feature tag 3gpp-application.ims.iari.v2x may indicatecapability for V2X which may be vehicle, pedestrian, infrastructure,vehicle-to-vehicle, vehicle-to-pedestrian, vehicle-to-network, and/orvehicle-to-infrastructure.

In one example, a feature tag 3gpp-application.ims.iari.v2x.emergencymay indicate capability for V2X which may be emergency vehicle,emergency pedestrian, emergency infrastructure, emergencyvehicle-to-vehicle, emergency vehicle-to-pedestrian, emergencyvehicle-to-network, and/or emergency vehicle-to-infrastructure.

In another example, one or more additional parameters may be included inthe new dialog establishment or a standalone transaction along with afeature tag to indicate the V2X device capability or a combination ofone or more capabilities of the V2X device.

In an implementation, the V2X UE may transmit the message to establish adialog, new dialog, or as a standalone transaction to a UE relay via PC5which relays message to the V2X AS via VC1. The V2X UE may discover theUE relay using discovery model A or model B. In an example, the UE relaymay decode the message for new dialog establishment or for thestandalone transition and may update the message headers beforeretransmitting the message. The UE relay may update the source anddestination address in the message for the new dialog and standalonetransaction.

The flow diagram in the example embodiment in FIG. 20 shows a V2X ASsends information about broadcast/multicast bearer to the V2X UE. FIG.20 shows that V2X AS may get the broadcast/multicast information fromMS-BC and pass on to the V2X UE by employing a dialog, a new dialog,and/or a standalone transaction which comprises one or more ICSIs of V2Xand/or one or more IARIs of V2X service/application and/or one or moreICSIs of V2X and/or one or more IARIs of broadcast/multicastservice/application. In one example embodiment, the information may beabout availability of broadcast/multicast bearer and the details for itsconnectivity. In one example embodiment, the information may be anupdate of the details of the broadcast/multicast bearer. In one exampleembodiment, the information may be the request for the release of thebroadcast/multicast bearer. In one example embodiment, the informationmay be about the unicast bearer. V2X UE may confirm V2X AS the receptionof the information.

The flow diagram in the example embodiment in FIG. 21 shows a V2X UEsends information about broadcast/multicast bearer to the V2X AS. FIG.21 shows that V2X UE may realize that it has lost thebroadcast/multicast bearer coverage and may request V2X AS an update forthe broadcast/multicast bearer by employing a dialog, a new dialog,and/or a standalone transaction which comprises one or more ICSIs of V2Xand/or one or more IARIs of V2X service/application and/or one or moreICSIs of V2X and/or one or more IARIs of broadcast/multicastservice/application. In one example embodiment, the information may beabout updating the details of the broadcast/multicast bearer. In oneexample embodiment, the information may be about releasing thebroadcast/multicast bearer and moving to the unicast bearer. V2X AS mayconfirm V2X UE the reception of the information.

V2X communication may rely on group discovery (e.g. the members of agroup discover each other in prior to the V2X group communications). TheV2X group communication may be either on-network or off-network. Theon-network V2X group communication may rely on having access to thenetwork while the off-network may be the direct communications among thegroup members without any network involvements.

Depending on the geographic pattern, locations, velocity, etc. themembers of a V2X group may come close to each other or get far apart.The V2X group members may need to keep track of each other by theperiodic V2X discovery mechanism. Examples for V2X direct discoverymethods are Model A and Model B.

Model A may include the following examples two roles for the V2X-enabledUEs that are participating in V2X direct discovery: announcing UE: a)The UE may announce certain information that may be used by UEs inproximity that have permission to discover, and b) monitoring a UE wherethe UE that may monitor certain information of interest in proximity ofannouncing UEs.

In Model A, the announcing UE may broadcast discovery messages atdiscovery intervals (e.g. pre-defined intervals) and the monitoring UEsthat are interested in these messages may read them and may processthem. In an example, this model may be equivalent to “I am here” sincethe announcing UE may broadcast information about itself e.g. its V2Xapplication code in the discovery message.

The UE may act as “announcing UE” in the carrier frequency signaled bythe serving PLMN when using Model A mode. The UE may act as a“monitoring” UE in the resources of the serving PLMN and local PLMNs,when using Model A mode. When inter-PLMN discovery transmission issupported, the carrier frequency may be operated by a PLMN other thanthe serving PLMN. Open and/or restricted discovery types may besupported by Model A. If V2X is not employed as a mission criticalfeature, the discovery may be open discovery. If V2X is employed formission critical communication, the discovery may be restricted.

Model B, when restricted discovery type is used, may include thefollowing examples two roles for the V2X-enabled UEs that areparticipating in V2X direct discovery: a) discoverer UE: The UE maytransmit a request containing certain information about what it isinterested to discover, and b) discoveree UE: The UE that may receivethe request message may respond with some information related to thediscoverer's request.

In an example embodiment, it may be equivalent to “who is there/are youthere.” The discoverer UE may send information about other UEs that maylike to receive responses. The information may be about a V2Xapplication identity corresponding to a group and the members of thegroup may respond.

When using Model B discovery, the discoverer UE and discoveree UE mayannounce in the carrier frequency signaled by the serving PLMN. Wheninter-PLMN discovery transmission is supported, the carrier frequencymay be operated by a PLMN other than the serving PLMN. The discoverer UEand discoveree UE may be allowed to monitor in the serving PLMN andLocal PLMNs when authorized. In an example implementation, onlyrestricted discovery type may be supported by Model B. In an exampleapplication, the public safety discovery may be considered restricted.The monitoring UE/discoverer UE may need to have authorization (such asthrough pre-provisioned parameters) to perform discovery of theappropriate service(s).

In one example embodiment, the V2X discovery may be considered open anddepending on Model A, it may use V2X application code for Model A. Inone example embodiment, the V2X discovery may be considered restrictedand depending on Model A or Model B, it may use V2X restrictedapplication code for Model A, it may use V2X query code/V2X responsecode respectively for Model B.

These code parameters may be n bits (e.g. 64 bits), and may be part ofV2X application code. In an example embodiment, the code parameters maycorrespond to one or more V2X application ID(s). In an exampleembodiment, where the restricted discovery may be used, the codeparameters may correspond to one or more restricted V2X application userID(s) (RPAUID). In an example embodiment, where the restricted discoverymay be used, the V2X application user ID may be allocated and bound toV2X discovery UE ID (PDUID) by the V2X application server.

The figure in the example embodiment in FIG. 22 shows an example V2Xdiscovery message which may be employed for discovery procedures inModel A and Model B. Model A may comprise procedures for the announcingV2X UE and procedures for the monitoring V2X UE. Model A may includematching procedure for the case when the monitoring V2X UE may receiveV2X code over the air that matches the discovery filter provided by theHPLMN V2X function to the monitoring V2X UE in the discovery responsemessage, however the corresponding V2X application identity orrestricted V2X application UE identity (RPAUID) may not have validvalidity timer.

The flow diagram in the example embodiment in FIG. 23 shows an exampleprocedure for Model A Discovery. This example procedure for the Model Adiscovery comprises authorization. In an example embodiment, the V2X UEmay get authorized for V2X direct discovery. In one example embodiment,if V2X service is restricted, the V2X UE may get authorized forrestricted V2X direct discovery. The procedure for the Model A discoverycomprises announcement which may be in one example embodiment, theannouncing V2X UE may request for discovery and may receive the V2Xapplication code (or V2X application code prefix and V2X applicationcode suffix(es), if the application-controlled extension is used). Theannouncing V2X UE may announce the V2X application code (or V2Xapplication code prefix and V2X application code suffix(es) if theapplication-controlled extension is used).

In an example embodiment, if V2X may use restricted discovery. Theannouncing V2X UE may request for discovery and may receive the V2Xrestricted code (or V2X restricted code prefix and V2X restricted codesuffix(es) to announce itself, if the application-controlled extensionis used). The announcing V2X UE may announce the V2X restricted code (orV2X restricted code prefix and V2X restricted code suffix(es), if theapplication-controlled extension is used).

The procedure for the Model A discovery may comprise monitoring whichmay be in one example embodiment. The monitoring V2X UE may request fordiscovery and may receive the V2X discovery filter(s) comprising the V2Xapplication ID (or V2X application ID prefix and V2X application IDsuffix(es), if the application-controlled extension is used). Themonitoring V2X UE may monitor for the V2X application ID (or V2Xapplication ID prefix and V2X application ID suffix(es), if theapplication-controlled extension is used). The monitoring UE maymatch-report if having monitored V2X application code that does notmatch the locally V2X application ID (or V2X application ID prefix andV2X application ID suffix(es), if the application-controlled extensionis used).

In an example embodiment, if the V2X service is restricted. Themonitoring V2X UE may request for discovery and may receive the V2Xdiscovery filter(s) comprising the V2X restricted code (or V2Xrestricted code prefix and V2X restricted code suffix(es), if theapplication-controlled extension is used). The monitoring V2X UE maymonitor for the V2X restricted code (or V2X restricted code prefix andV2X restricted code suffix(es), if the application-controlled extensionis used). The monitoring UE may match-report if having monitored V2Xrestricted code (or V2X restricted code prefix and V2X restricted codesuffix(es), if the application-controlled extension is used) matches thediscovery filter but the corresponding PRAUID associated with it, doesnot have a valid validity timer.

The flow diagram in the example embodiment in FIG. 24 shows an exampleprocedure for announcing V2X UE. The procedure for the announcing V2X UEcomprises in one example embodiment, if discovery is not restricted, theV2XUE may be configured with V2X application ID corresponding to theHPLMN. If the discovery is restricted, the application client in the V2XUE may retrieve the V2X discovery UE identity (PDUID) and may provide itto the V2X application server. The V2X application server may allocate arestricted V2X application UE identity (RPAUID) for that PDUID, maystore the binding between the PDUID and the RPAUID and may return theRPAUID to the application client in the V2X UE. V2X UE may use RPAUIDinstead of PDUID since the announcement is restricted.

In one example embodiment, if discovery is not restricted, the V2X UEmay construct a discovery request message comprising a V2X applicationID, UE identity set to international mobile subscriber identity (IMSI),command=announce, discovery type set to open discovery, application IDset to unique identifier of the V2X application ID, discovery entry IDindicating if this is a new request, optional requested discovery timerset to validity timer associated with the expected V2X restricted codefrom the HPLMN V2X function (if it is set to zero, the V2X UE isrequesting to remove the discovery entity ID and release the associatedresources), (if application-controlled extension may be used)application level container containing the request and the relevantinformation, and the PLMN ID of the carrier frequency in announcing PLMNID if the serving PLMN signaled carrier frequency is not operated byHPLMN or VPLMN and if inter-PLMN V2X discovery transmission issupported. V2X UE may send the discovery request message to HPLMN V2Xfunction. If the discovery is restricted, the V2X UE may construct adiscovery request message comprising RPAUID, UE identity set tointernational mobile subscriber identity (IMSI), command=announce,discovery type set to restricted discovery, application ID set to uniqueidentifier of the V2X application ID, discovery entry ID indicating ifthis is a new request, optional requested discovery timer set tovalidity timer associated with the expected V2X restricted code from theHPLMN V2X function (if it is set to zero, the V2X UE is requesting toremove the discovery entity ID and release the associated resources),(if application-controlled extension may be used) application levelcontainer containing the request and the relevant information,announcing type such as “on demand” for the indicated application, andthe PLMN ID of the carrier frequency in announcing PLMN ID if theserving PLMN signaled carrier frequency is not operated by HPLMN orVPLMN and if inter-PLMN V2X discovery transmission is supported. V2X UEmay send the discovery request message to HPLMN V2X function.

In one example embodiment, if the discovery is not restricted, HPLMN V2Xfunction may check for authorization for the V2X application. If thereis not any associated V2X UE context, the HPLMN V2X function may checkwith HSS and if needed may create a new context for the V2X UE that maycontain the subscription parameters for this V2X UE. HSS may alsoprovide a MSISDN of the V2X UE and PLMN ID of where the V2X UE isregistered. If the discovery is restricted, HPLMN V2X function may checkfor authorization for the V2X application. If there is not anyassociated V2X UE context, the HPLMN V2X function may check with HSS andif needed may create a new context for the V2X UE that may contain thesubscription parameters for this V2X UE. HSS may provide also MSISDN ofthe V2X UE and PLMN ID of where the V2X UE is registered.

In one example embodiment, if the discovery is not restricted, the HPLMNV2X function may send an authorization request comprising a V2Xapplication ID and request type set to “open discovery/announce” towardsthe V2X application server. The authorization request may containallowed number of suffixes if open direct discovery withapplication-controlled extension is used. The request type may be set to“open discovery with application-controlled extension/announce”. If thediscovery is restricted, the HPLMN V2X function may send anauthorization request comprising RPAUID and request type set to“restricted discovery/announce” towards the V2X application server. Theauthorization request may contain an allowed number of suffixes ifrestricted direct discovery with application-controlled extension isused. The request type may be set to “restricted discovery withapplication-controlled extension/announce”.

In one example embodiment, if the discovery is not restricted, the V2Xapplication server may answer by an authorization response comprisingresponse type set to “open discover/announce ack”. The authorizationrespond may include V2X application code suffix pool with allocatedsuffixes by the V2X application if the open direct discovery withapplication-controlled extension is used. The response type may be setto “open discovery with application-controlled extension/announce ack”.If the discovery is restricted, the V2X application server may answer byan authorization response comprising PDUID(s) corresponding the RPAUIDstored in the V2X application server and response type set to“restricted discover/announce ack.” The authorization respond mayinclude V2X restricted code suffix pool with allocated suffixes by theV2X application if restricted direct discovery withapplication-controlled extension is used. The response type may be setto “restricted discovery with application-controlled extension/announceack”.

In one example embodiment, if the discovery is restricted, the HPLMN V2Xfunction may assign a V2X restricted code corresponding to the RPAUID inthe discovery request and an associated validity timer which mayidentify the duration of validity of the V2X restricted code. The V2X UEmay use this V2X restricted code within this validity duration if PLMNis not changed. If restricted direct discovery withapplication-controlled is used, then the HPLMN V2X functions may assigna V2X restricted code prefix instead of V2X restricted code. Ifdiscovery request message indicates “on demand” announcing and the “ondemand” announcing is authorized and enabled based on application ID andoperator's policy, the HPLMN V2X function may store RPAUID, V2Xrestricted code (or V2X restricted code prefix) with the associatedvalidity timer, and enabled indicator in the user context. “On demand”announcing may be activated based on an ongoing monitoring request,otherwise, the following steps are not executed.

In one example embodiment, if the discovery is not restricted, the HPLMNV2X function may check whether the V2X UE is authorized to use the V2Xapplication ID in the original request. If V2X UE is authorized, theHPLMN V2X function may inform the PLMN where the V2X UE is visiting bysending an announce authorization comprising V2X application ID, V2Xapplication code (or V2X application code prefix and V2X applicationcode suffixes if application-controlled extension is used), V2X UEidentity set to IMSI or mobile station identifier number (MSISDN),validity timer for charging purposes, and showing how long the V2Xapplication code is valid discovery entry ID, and possible metadata. Ifthe discovery is restricted, if the discovery request is authorized,HPLMN V2X function may construct announce authorization messagecontaining RPAUID, V2X application ID, V2X restricted code (or V2Xrestricted code prefix with V2X restricted code suffix pool ifrestricted direct discovery with application-controlled extension isused) set to assigned code for this request, UE ID set to IMSI or mobilestation identifier number (MSISDN), discovery entry ID, and validitytimer. The HPLMN V2X function may update the existing announcing V2XUE's discovery entry with the new V2X restricted code (or the V2Xrestricted code prefix with V2X restricted code suffix pool ifrestricted direct discovery with application-controlled extension isused) and the new validity timer by using the V2X UE's correspondingdiscovery entry ID included in the discovery request message. Ifdiscovery request message included discovery timer set to zero for adiscovery entity ID, then the HPLMN V2X function informs the VPLMN V2Xfunction to remove resources for that discovery entry ID by setting thetimer to zero. The HPLMN V2X function may send the announceauthorization message towards the VPLMN V2X function.

In one example embodiment, if the discovery is not restricted, the VPLMNV2X function may acknowledge the HPLMN V2X function that it mayauthorize the V2X UE to perform open discovery announcing if theannounce authorization message contain a new discovery entry ID. If thediscovery entry ID already exists, the VPLMN V2X function mayacknowledge the update as requested. If the discovery is restricted, theVPLMN V2X function may acknowledge the HPLMN V2X function that it mayauthorize the V2X UE to perform restricted discovery announcing if theannounce authorization message contain a new discovery entry ID. If thediscovery entry ID already exists, the VPLMN V2X function mayacknowledge the update as requested.

In one example embodiment, if the discovery is not restricted, the HPLMNV2X function may construct a discovery respond message with V2Xapplication code (or V2X application code prefix with V2X applicationcode suffix pool if open direct discovery with application-controlledextension is used), validity timer, and discovery entity ID. Thevalidity timer is set to zero if it is zero in discovery request messageoriginated by the V2X UE. The HPLMN V2X function may send the discoveryrespond message towards the V2X UE. If the discovery is restricted andif the announcing is not “on-demand”, the HPLMN V2X function mayconstruct a discovery respond message with V2X restricted code (or V2Xrestricted code prefix with V2X restricted code suffix pool ifrestricted direct discovery with application-controlled extension isused), validity timer, and discovery entity ID. If the announcing is“on-demand” and is authorized and enabled, the HPLMN V2X function mayconstruct the discovery respond message with validity timer, announcingenabled indicator, and discovery entity ID. The validity timer is set tozero if it is zero in discovery request message originated by the V2XUE. The HPLMN V2X function may send the discovery respond messagetowards the V2X UE.

In one example embodiment, if the discovery is not restricted, V2X UEmay start announcing the provided V2X restricted code. If restricteddirect discovery with application-controlled extension is used, the V2XUE appends a V2X restricted code suffix from the received V2X restrictedcode suffix pool to the V2X restricted code prefix to form a V2Xrestricted code. The V2X UE may use different suffixes from the providedV2X restricted code suffix pool to form and announce different V2Xrestricted codes without having to contact the HPLMN V2X function aslong as the validity timer permits. If the discovery is restricted, V2XUE may start announcing the provided V2X restricted code. If restricteddirect discovery with application-controlled extension is used, the V2XUE appends a V2X restricted code suffix from the received V2X restrictedcode suffix pool to the V2X restricted code prefix to form a V2Xrestricted code. The V2X UE may use different suffixes from the providedV2X restricted code suffix pool to form and announce different V2Xrestricted codes without having to contact the HPLMN V2X function aslong as the validity timer permits. If “on-demand” announcing is usedand the HPLMN V2X function has not provided V2X restricted code (or V2Xrestricted code prefix with V2X restricted code suffix pool ifrestricted direct discovery with application-controlled extension isused), the V2X UE may need to wait for an announcing alert requestmessage from the HPLMN V2X function before announcing on PC5 interface.

The flow diagram in the example embodiment in FIG. 25 shows an exampleprocedure for monitoring V2X UE. The procedure for monitoring V2X UEcomprises in one example embodiment, if the discovery is not restricted,the V2X UE may be configured for V2X application ID corresponding thePLMN where the UE is authorized to monitor. If the discovery isrestricted, the application client in the V2X UE may retrieve the V2Xdiscovery UE identity (PDUID) and may provide it to the V2X applicationserver. The V2X application server may allocate a restricted V2Xapplication UE identity (RPAUID) for that PDUID, may store the bindingbetween the PDUID and the RPAUID and may return the RPAUID to theapplication client in the V2X UE. The V2X UE may obtain RPAUIDs of thoseV2X target users from the V2X application server passed in anapplication level container. V2X may use RPAUID instead of PDUID if thediscovery is restricted.

In one example embodiment, if the discovery is not restricted, in orderto get the discovery filter, the monitoring V2X UE may construct adiscovery request message comprising V2X application ID, UE identity setto e.g. IMSI, command=monitor, discovery type, application ID set tounique identifier for the application that may have triggered discoveryprocedure, possible application level container comprising the targetV2X application code suffix that the V2X UE is to monitor, discoveryentry ID showing the discovery identity that it is a new discovery or anexisting one, and the optional requested discovery timer. The requesteddiscovery timer may be set to zero to indicate HPLMN to delete thediscovery filter(s) for that discovery entry ID. The application levelcontainer may include some information about V2X application code suffixsuch as group or user specific information if direct discovery withapplication-controlled extension may be used. The V2X UE may send thediscovery request message towards HPLMN V2X function. If the discoveryis restricted, in order to get the discovery filter, the monitoring V2XUE may construct a discovery request message comprising RPAUID set tothe monitoring V2X UE identity, UE identity set to IMSI,command=monitor, discovery type, application ID set to unique identifierfor the application that may have triggered discovery procedure,application level container comprising the target RPAUIDs that the V2XUE is to monitor, discovery entry ID showing the discovery identity thatit is a new discovery or an existing one, and the optional requesteddiscovery timer. The requested discovery timer is set to zero toindicate HPLMN to delete the discovery filter(s) for that discoveryentry ID. The application level container may include some informationabout V2X restricted code suffix such as group or user specificinformation if direct discovery with application-controlled extension isused. The V2X UE may send the discovery request message towards HPLMNV2X function.

In one example embodiment, if the discovery is not restricted, the HPLMNV2X function may check for authorization for the V2X application. Ifthere is not any associated V2X UE context, the HPLMN V2X function maycheck with HSS and if needed may create a new context for the V2X UEthat may contain the subscription parameters for this V2X UE. HSS mayprovide also MSISDN of the V2X UE and PLMN ID of where the V2X UE isregistered. If the discovery is restricted, the HPLMN V2X function maycheck for authorization for the V2X application. If there is not anyassociated V2X UE context, the HPLMN V2X function may check with HSS andif needed may create a new context for the V2X UE that may contain thesubscription parameters for this V2X UE. HSS may provide also MSISDN ofthe V2X UE and PLMN ID of where the V2X UE is registered.

In one example embodiment, if the discovery is restricted, the HPLMN V2Xfunction may send an authorization request comprising V2X application IDand request type set to “open discovery/monitor” towards the V2Xapplication server. If open direct discovery with application-controlledextension is used, the request type is then set to “open discovery withapplication-controlled extension/monitor”. If the discovery isrestricted, the HPLMN V2X function may send an authorization requestcomprising RPAUID and request type set to “restricted discovery/monitor”towards the V2X application server. If restricted direct discovery withapplication-controlled extension is used, the request type is then setto “restricted discovery with application-controlled extension/monitor.”

In one example embodiment, if the discovery is not restricted, the V2Xapplication server may construct an authorization response comprisingmask(s) for V2X application code suffix(es) corresponding to V2Xapplication ID and response type set to “open discovery/monitor ack” (orto “open discovery with application-controlled extension/monitor ack” ifo direct discovery with application-controlled extension is used). TheV2X application server may send the authorization response towards theHPLMN

V2X function. If the discovery is restricted, the V2X application servermay construct an authorization response comprising target PDUIDs andcorresponding target RPAUID that the RPAUID in the authorization requestmay monitor, PDUID of the requesting V2X UE, and response type set to“restricted discovery/monitor ack” (or to “restricted discovery withapplication-controlled extension/monitor ack” if restricted directdiscovery with application-controlled extension is used). The V2Xapplication server may send the authorization response towards the HPLMNV2X function.

In one example embodiment, if the discovery is not restricted, the HPLMNV2X function may construct a monitor request message comprising V2Xapplication ID of monitoring V2X UE which is set to the uniqueidentifier for the application that may have triggered the discoveryprocedure, UE identity set to IMSI or MSISDN, V2X application codesuffix(es) and corresponding mask(s), and discovery entry ID to identifythe discovery entry being new or an existing one. The HPLMN V2X functionmay send the monitor request towards the target PLMN V2X function whichmay belong to the monitoring V2X UE. If the discovery entry ID is anexisting one, the target PLMN V2X function may modify the existingdiscovery procedure with the parameters included in the monitor requestmessage. If the discovery is restricted, the HPLMN V2X function mayconstruct a monitor request message comprising RPAUID of monitoring V2XUE, UE identity set to IMSI or MSISDN, target PDUID and correspondingtarget RPAUID, application ID set to unique identifier for applicationthat may have triggered the discovery procedure, and discovery entry IDto identify the discovery entry being new or an existing one. The HPLMNV2X function may send the monitor request towards the target PLMN V2Xfunction which may belong to the monitoring V2X UE. If the discoveryentry ID is an existing one, the target PLMN V2X function may modify theexisting discovery procedure with the parameters included in the monitorrequest message.

In one example embodiment, if the discovery is restricted, the targetPLMN V2X function may retrieve the V2X restricted code (or the V2Xrestricted code prefix if the restricted direct discovery withapplication-controlled extension is used) corresponding to the targetedPDUID, targeted RPAUID, and application ID. If in the context of theannouncing V2X UE, the announcing enabled indicator is stored, thetarget PLMN V2X function may construct an announcing alert requestmessage comprising RPAUID indicating which monitoring V2X UE isinterested in the targeted V2X UE announcement, application ID set tounique identifier for the application that may have triggered discoveryprocedure, V2X restricted code retrieved from the context of thetargeted announcing V2X UE (or V2X restricted code prefix with V2Xrestricted code suffix pool if restricted direct discovery withapplication-controlled extension was requested by the announcing V2XUE), and discovery entry ID to indicate it is a new discovery entity oran existing one. The target PLMN V2X function may send the messagetowards the targeted V2X UE and upon receipt of the announce alertresponse message from that V2X announcing UE, the V2X function removesthe announcing enabled indication associated to the V2X restricted code(or V2X restricted code prefix with V2X restricted code suffix pool ifrestricted direct discovery with application-controlled extension wasrequested by the announcing V2X UE) from the announcing V2X UE context.The V2X UE may now start announcing the V2X restricted code (or V2Xrestricted code prefix with V2X restricted code suffix pool ifrestricted direct discovery with application-controlled extension wasrequested by the announcing V2X UE).

In one example embodiment, the target V2X function may have an option toconstruct an authorization request message comprising RPAUID set to thatof the monitoring V2X UE, request type set to “restricteddiscovery/permission”, and target RPAUID set to that of the announcingV2X UE. The target V2X function may send the authorization requestmessage towards the V2X application server.

In one example embodiment, the V2X application server may acknowledgethe target V2X function by constructing an authorization responsemessage comprising PDUID of the announcing V2X UE which may be monitoredand response type set to “restricted discovery/permission ack” andsending it towards the target PLMN V2X function.

In one example embodiment, if the discovery is not restricted, thetarget V2X function may construct a monitor response message comprisingV2X application code (or V2X application code prefix with V2Xapplication code suffix pool if open direct discovery withapplication-controlled extension was requested by the announcing V2X UE)and the corresponding validity timer. The target V2X function may sendthe monitor response message towards the HPLMN V2X function. If thediscovery is restricted, the target V2X function may construct a monitorresponse message comprising V2X restricted code (or V2X restricted codeprefix with V2X restricted code suffix pool if restricted directdiscovery with application-controlled extension was requested by theannouncing V2X UE) and the corresponding validity timer. The target V2Xfunction may send the monitor response message towards the HPLMN V2Xfunction.

In one example embodiment, if the discovery is not restricted, from theV2X application server, the HPLMN V2X function has now retrieved the V2Xapplication code (or V2X application code prefix with V2X applicationcode suffix pool if open direct discovery with application-controlledextension was requested by the announcing V2X UE). The HPLMN V2Xfunction based on the V2X application code (or V2X application codeprefix with V2X application code suffix pool if restricted directdiscovery with application-controlled extension was requested by theannouncing V2X UE) and the corresponding validity timer, may allocate adiscovery filter with corresponding time-to-live (TTL). If the discoveryis restricted, from the V2X application server, the HPLMN V2X functionhas now retrieved the V2X restricted code (or V2X restricted code prefixwith V2X restricted code suffix pool if restricted direct discovery withapplication-controlled extension was requested by the announcing V2X UE)and the corresponding validity timer for each pair of targetPDUID-target RPAUID bound with application ID and stored as the usercontent of the monitoring V2X UE. The HPLMN V2X function based on theV2X restricted code (or V2X restricted code prefix with V2X restrictedcode suffix pool if restricted direct discovery withapplication-controlled extension was requested by the announcing V2X UE)and the corresponding validity timer, may allocate a discovery filterwith corresponding time-to-live (TTL).

In one example embodiment, if the discovery is not restricted, the HPLMNV2X function may construct a discovery response message comprisingdiscovery filter(s) that may comprise V2X application code (or V2Xapplication code prefix with V2X application code suffix pool if opendirect discovery with application-controlled extension was requested bythe announcing V2X UE) to be monitored and the corresponding TTL showinghow long the filter is valid. If the requested discovery timer indiscovery request message sent by V2X monitoring UE was set to zero, theTTL in the discovery response message may be set to zero. The discoveryresponse message may comprise discovery entry ID to identify thediscovery entity. The HPLMN V2X function may send the discovery responsemessage towards the monitoring V2X UE. If the discovery is restricted,the HPLMN V2X function may construct a discovery response messagecomprising target RPAUID(s) and the corresponding discovery filter(s)that may comprise V2X restricted code (or V2X restricted code prefixwith V2X restricted code suffix pool if restricted direct discovery withapplication-controlled extension was requested by the announcing V2X UE)to be monitored and the corresponding TTL showing how long the filter isvalid. If the requested discovery timer in discovery request messagesent by V2X monitoring UE was set to zero, the TTL in the discoveryresponse message may be set to zero. The discovery response message maycomprise discovery entry ID to identify the discovery entity. The HPLMNV2X function may send the discovery response message towards themonitoring V2X UE. The V2X UE may use the discovery filter to monitorthe announcing V2X UE.

The flow diagram in the example embodiment in FIG. 26 shows theprocedure for the match report. The procedure for match report forannouncing/monitoring comprises in one example embodiment, if thediscovery is not restricted, if the monitoring V2X UE may have over theair received a V2X application code (or the V2X application code prefixand the V2X application code suffix if the restricted direct discoverywith application-controlled extension is used) is matching the discoveryfilter obtained in the discovery response message from the HPLMN V2Xfunction but the announcing V2X UE does not have an V2X application IDthat matches the one that locally stored or its metadata is differentfrom the one that locally stored, the monitoring V2X UE may construct amatch report message comprising V2X application ID set to uniqueidentifier for the application that may have triggered the monitoringrequest, IMSI or MSISDN as UE identity, discovery type set to “opendiscovery”, the over the air received V2X application code, optionalmetadata requested, and announcing PLMN ID of the PLMN where theannouncing V2X UE was monitored. The monitoring V2X UE may transmit thematch report message towards the HPLMN V2X function. If the discovery isrestricted, if the monitoring V2X UE may have over the air received aV2X restricted code (or the V2X restricted code prefix and the V2Xrestricted code suffix if the restricted direct discovery withapplication-controlled extension is used) is matching the discoveryfilter obtained in the discovery response message from the HPLMN V2Xfunction but the announcing V2X UE does not have an RPAUID with a validTTL, the monitoring V2X UE may construct a match report messagecomprising its own RPAUID, its IMSI or MSISDN as UE identity, discoverytype set to “restricted discovery”, application ID set to uniqueidentifier for the application that may have triggered the monitoringrequest, the over the air received V2X restricted code, optionalmetadata requested, and announcing PLMN ID of the PLMN where theannouncing V2X UE was monitored. The monitoring V2X UE may transmit thematch report message towards the HPLMN V2X function.

In one example embodiment, if the discovery is not restricted, the HPLMNV2X function may verify if the monitoring V2X UE may perform opendiscovery and may analyze V2X application code (or the V2X applicationcode prefix and the V2X application code suffix if the open directdiscovery with application-controlled extension is used). The HPLMN V2Xfunction identifies the announcing V2X UE's V2X application code in thecontext of the monitoring V2X UE. If the discovery is restricted, theHPLMN V2X function may verify if the monitoring V2X UE may performrestricted discovery and may analyze V2X restricted code (or the V2Xrestricted code prefix and the V2X restricted code suffix if therestricted direct discovery with application-controlled extension isused). The HPLMN V2X function identifies the announcing V2X UE's RPAUIDin the context of the monitoring V2X UE.

In one example embodiment, if the discovery is restricted, if metadatarequested was included to the originated match report message by themonitoring V2X UE, the HPLMN V2X function may locate the V2X applicationserver from the application ID and may construct an authorizationrequest message comprising monitoring V2X UE's RPAUID, announcing V2XUE's RPAUID, and request type set to “restricted discovery/match”. TheHPLMN V2X function may send the authorization request message towardsthe V2X application server. This step is optional if metadata requestedwas not included into the original match report message.

In one example embodiment, if the discovery is restricted the V2Xapplication server may construct an authorization response comprisingmonitoring V2X UE's PDUID, announcing V2X UE's PDUID, response type setto “restricted discovery/match ack”, and metadata corresponding to theannouncing V2X UE.

In one example embodiment, if the discovery is not restricted, the HPLMNV2X function may verify that the V2X application ID may belong to themonitoring V2X UE and the announcing V2X UE's V2X application ID are thesame as the announcing V2X UE's V2X application ID that is stored in thecontext of the monitoring V2X UE. If the discovery is restricted, theHPLMN V2X function may verify that the PDUID may belong to themonitoring V2X UE and the announcing V2X UE's PDUID are the same as theannouncing V2X UE's PDUID that is stored in the context of themonitoring V2X UE.

In one example embodiment, if the discovery is not restricted, the HPLMNV2X function may construct a match report ack comprising V2X applicationID set to unique identifier for the application that may have triggeredthe monitoring request, announcing V2X UE's V2X application ID, validitytimer, and optionally metadata. If the discovery is restricted, theHPLMN V2X function may construct a match report ack comprising V2Xapplication ID set to unique identifier for the application that mayhave triggered the monitoring request, announcing V2X UE's RPAUID,validity timer, and optionally metadata.

In one example embodiment, if the discovery is restricted, themonitoring V2X UE may store the mapping between the V2X restricted code(or the V2X restricted code prefix and the V2X restricted code suffix ifthe restricted direct discovery with application-controlled extension isused), announcing V2X UE's V2X application ID, the application ID uniqueidentifier of the application that may have triggered the monitoringprocedure, and the related validity timer. If the discovery isrestricted, the monitoring V2X UE may store the mapping between the V2Xrestricted code (or the V2X restricted code prefix and the V2Xrestricted code suffix if the restricted direct discovery withapplication-controlled extension is used), announcing V2X UE's PRAUID,the application ID unique identifier of the application that may havetriggered the monitoring procedure, and the related validity timer.

In one example embodiment, if the discovery is not restricted, the HPLMNV2X function may construct a match report info message comprisingmonitoring V2X UE's V2X application ID, announcing V2X UE's V2Xapplication ID, announcing V2X UE's identity set to IMSI or MSISDN forcharging purposes, V2X application code (or the V2X application codeprefix and the V2X application code suffix if the open direct discoverywith application-controlled extension is used), and discovery type setto “open discovery”. The HPLMN V2X function may send the match reportinfo message towards the announcing V2X UE's PLMN V2X function and theV2X function of the PLMN where the announcing V2X UE may be roaming in.If the discovery is restricted, the HPLMN V2X function may construct amatch report info message comprising monitoring V2X UE's RPAUID,announcing V2X UE's RPAUID, announcing V2X UE's identity set to IMSI orMSISDN for charging purposes, V2X restricted code (or the V2X restrictedcode prefix and the V2X restricted code suffix if the restricted directdiscovery with application-controlled extension is used), and discoverytype set to “restricted discovery”. The HPLMN V2X function may send thematch report info message towards the announcing V2X UE's PLMN V2Xfunction and the V2X function of the PLMN where the announcing V2X UEmay be roaming in.

Model B may comprise procedure for the discoveree V2X UE and procedurefor the discoverer V2X UE procedure. It may include matching procedurefor the case when the discoverer V2X UE may receive V2X response codeover the air that may match the discovery filter provided by the HPLMNV2X function to the discoveree V2X UE in the discovery response message,however the corresponding V2X application ID may not have valid validitytimer. Model B may always be for restricted discovery.

The flow diagram in the example embodiment in FIG. 27 shows an exampleprocedure for Model B Discovery. The procedure for the Model B discoverymay comprise authorization which may be the V2X UE may get authorizedfor restricted V2X direct discovery. In one example embodiment, the V2Xdirect discovery may need to be restricted. Model B discovery maycomprise discoveree Procedure which may be the discoveree V2X UE mayrequest for discovery and may receive the V2X response code andassociated discovery query filter(s). The discoveree V2X UE may employthe discovery filter(s) to monitor V2X query code on PC5. The discovereeV2X UE may announce the V2X response code if receiving a V2X query codeover the air which matches any of discovery filter(s).

Model B discovery may comprise discoverer procedure which may be thediscoverer V2X UE may request for discovery and may receive the V2Xquery code and associated discovery response filter(s). The discovererV2X UE may announce the V2X query code on PC5 interface. The discovererV2X UE may monitor V2X response code on PC5 interface that matches anyof the discovery response filter(s). The discoverer UE may match-reportif having discovered V2X response code with corresponding V2Xapplication ID with no valid validity timer. The discoveree, discoverer,and match-report procedures are explained later in this context.

The flow diagram in the example embodiment in FIG. 28 shows an exampleprocedure for discoveree V2X UE. The procedure for discoveree V2X UEcomprises the application client in the V2X UE may retrieve the V2Xdiscovery UE identity (PDUID) and may provide it to the V2X applicationserver. The V2X application server may allocate a restricted V2Xapplication UE identity (RPAUID) for that PDUID, may store the bindingbetween the PDUID and the RPAUID and may return the RPAUID to theapplication client in the V2X UE. The application client in the V2X UEmay store the binding between the RPAUID and its own PDUID and may usethose RPAUID to perform discoveree request procedure.

The discoveree V2X UE may establish connection to HPLMN V2X function andmay construct a discovery request message comprising RPAUID set to whatthe V2X UE may announce, UE identity set to IMSI, command indicatingthis is for discoveree UE, discovery type set to “restricted discovery”,discovery Model indicating Model B, application ID set to uniqueidentifier for the application that may have triggered discoveryprocedure, discovery entry ID showing the discovery identity that it isa new discovery or an existing one, and PLMN ID of the carrier frequencyin announcing PLMN ID if the serving PLMN signaled carrier frequency isnot operated by HPLMN or VPLMN and if inter-PLMN V2X discoverytransmission is supported. V2X UE may send the discovery request messageto HPLMN V2X function.

HPLMN V2X function may check for authorization for the V2X application.If there is not any associated V2X UE context, the HPLMN V2X functionmay check with HSS and if needed may create a new context for the V2X UEthat may contain the subscription parameters for this V2X UE. HSS mayprovide also MSISDN of the V2X UE and PLMN ID of where the V2X UE isregistered.

The HPLMN V2X function may locate the V2X application server based onthe application ID in the discovery request message and may send anauthorization request containing RPAUID and request type set to“restricted discovery/response” towards the V2X application server.

The V2X application server answers by an authorization responsecontaining PDUID(s) corresponding the RPAUID stored in the V2Xapplication server and response type set to “restricteddiscover/response ack”.

The HPLMN V2X function may verify that at least of one of the PDUID(s)may belong to the discoveree V2X UE. The HPLMN V2X function assigns aV2X response code and V2X query code with the associated discovery queryfilter(s). The V2X response code corresponds to the RPAUID in thediscovery request and the HPLMN V2X function assigns an associatedvalidity timer for the V2X response code and V2X query code with theassociated discovery query filter(s). The validity timer identifies theduration of validity of the V2X response code and V2X query code withthe associated discovery query filter(s). The discoveree V2X UE may usethis V2X response code within this validity duration if PLMN is notchanged. The HPLMN V2X function may store V2X response code with itsassociated validity timer and V2X query code with associated discoveryquery filter(s) in the context of the V2X user.

If the discovery request is authorized, HPLMN V2X function may constructannounce authorization message containing RPAUID, V2X application ID,V2X response set to assigned code for this request, UE ID set to IMSI orMSISDN, discovery entry ID to identify the discovery entry, and validitytimer indicating how long the V2X response code will be valid. The HPLMNV2X function may send the announce authorization message towards theVPLMN V2X function.

The VPLMN V2X function may acknowledge the HPLMN V2X function that itmay authorize the V2X UE to perform restricted discovery announcing ifthe announce authorization message contain a new discovery entry ID. Ifthe discovery entry ID already exists, the VPLMN V2X function mayacknowledge the update as requested i.e. updating the discoveree V2XUE's discovery entry by the new V2X response code and its associatedvalidity timer.

The HPLMN V2X function may construct a discovery response message withdiscovery type set to Model B, V2X response code, discovery queryfilter(s) matched for certain V2X query code, validity timer associatedto V2X response code and the discovery query filter(s), and discoveryentity ID to identify the discovery identity. The V2X discoveree UE mayuse the discovery query filter(s) (which may be multiple) to determinewhich V2X query code may trigger that the V2X discoveree UE may announcethe assigned V2X response code. The HPLMN V2X function may send thediscovery response message towards V2X discoveree UE.

The V2X discoveree UE may use the discovery query filter(s) which may bemultiple to determine which V2X query code may trigger that the V2Xdiscoveree UE announces the assigned V2X response code. If the validitytimer expires, the V2X discoveree UE may send a new discovery requestmessage towards the HPLMN V2X function.

The flow diagram in the example embodiment in FIG. 29 shows an exampleprocedure for discoverer V2X UE. The procedure for discoverer V2X UEcomprises the application client in the V2X UE may retrieve the V2Xdiscovery UE identity (PDUID) and may provide it to the V2X applicationserver. The V2X application server may allocate a restricted V2Xapplication UE identity (RPAUID) for that PDUID, may store the bindingbetween the PDUID and the RPAUID and may return the RPAUID to theapplication client in the V2X UE. The V2X UE may obtain also RPAUIDs ofthose V2X target users from the V2X application server passed in anapplication level container. RPAUID instead of PDUID may be used sincethis is restricted discovery.

The discoverer V2X UE may establish connection to the MPLMN V2X functionand may construct a discovery request message comprising RPAUID set towhat the discoverer V2X UE wants to announce, UE identity set to IMSI,command showing this is for V2X query procedure, discovery type set to“restricted discover”, discovery Model set to Model B, application IDset to unique identifier for the application that may have triggereddiscovery procedure, application level container comprising the targetRPAUIDs that the V2X UE is to discover, discovery entry ID showing thediscovery identity that it is a new discovery or an existing one, andthe optional requested discovery timer. The requested discovery timermay be set to zero to indicate HPLMN to delete the discovery filter(s)for that discovery entry ID. The V2X UE may send the discovery requestmessage towards HPLMN V2X function.

HPLMN V2X function may check for authorization for the V2X application.If there is not any associated V2X UE context, the HPLMN V2X functionmay check with HSS and if needed may create a new context for the V2X UEthat may contain the subscription parameters for this V2X UE. HSS mayprovide also MSISDN of the V2X UE and PLMN ID of where the V2X UE isregistered.

The HPLMN V2X function may locate the V2X application server based onthe application ID in the discovery request message and may send anauthorization request containing RPAUID, request type set to “restricteddiscovery/query”, and application level container towards the V2Xapplication server.

The V2X application server may construct an authorization responsecomprising target PDUIDs and corresponding target RPAUID that the RPAUIDin the authorization request may discover, PDUID of the requesting V2XUE, and response type set to “restricted discovery/query ack”. The V2Xapplication server may send the authorization response towards the HPLMNV2X function.

The HPLMN V2X function may allocate the context for the discoveree UE(s)if the PLMN ID in the target PDUID-target RPAUID corresponds to a validV2X response code. The HPLMN V2X function may allocate the discoveryresponse filter(s) which trigger the V2X discoveree UE to transmit theV2X response code. This procedure has expiration time which is specifiedby validity timer.

The HPLMN V2X function may construct a discovery request messagecomprising RPAUID of discoveree V2X UE, UE identity set to IMSI orMSISDN, target PDUID and corresponding target RPAUID, application ID setto unique identifier for application that may have triggered thediscovery procedure, and discovery entry ID to identify the discoveryentry being new or an existing one. The HPLMN V2X function may send thediscovery request towards the target PLMN V2X function which may belongto the discoveree V2X UE. If the discovery entry ID is an existing one,the target PLMN V2X function may modify the existing discovery procedurewith the parameters included in the discovery request message.

The target V2X function has an option to construct an authorizationrequest message comprising RPAUID set to that of the discoverer V2X UE,request type set to “restricted discovery/query”, and target RPAUID setto that of the discoveree V2X UE. The target V2X function may send theauthorization request message towards the V2X application server.

The V2X application server may acknowledge the target V2X function byconstructing an authorization response message comprising PDUID of thediscovery V2X UE, response type set to “restricted discovery/query ack”,and target PDUID of the discoveree V2X UE. The V2X application servermay send the authorization response message towards the target PLMN V2Xfunction.

The target PLMN V2X function may allocate the context of the discovereeV2X UE based on target PDUID-target RPAUID and the application ID. Thetarget PLMN V2X function responds with a discovery response comprisingV2X query code which will be used by HPLMN V2X function to build thediscovery query filter so that it may trigger the discoveree UE to maysend V2X response code, the actual V2X response code, and validity timerto indicate for how long the V2X query code and V2X response code arevalid.

The HPLMN V2X function may construct an announce authorization messagecomprising RPAUID of the discovery V2X UE, application ID, V2X querycode and its associated validity timer, UE identity set to IMSI orMSISDN of discovery V2X UE for charging purposes in the visiting domain,and discovery entry ID to identify the discovery entry. The HPLMN V2Xfunction may send the announce authorization message towards the VPLMNV2X function.

The VPLMN may acknowledge that it may authorize the discovery V2X UE toperform V2X direct discovery procedure. If the discovery entry ID in theannounce authorization message corresponded an already discovery entry,the VPLMN V2X function may acknowledge the replacement of the existingV2X query code and its associated validity timer.

The HPLMN V2X function may construct the discovery response messagecomprising discovery model set to Model B, V2X query code, one ormultiple discovery response filters which are generated by the HPLMN V2Xfunction based on V2X response code, and validity timer for how long theV2X query code and discovery response filter(s) are valid. The HPLMN V2Xfunction may transmit the discovery response message to the discovererV2X UE.

The discoverer V2X UE may obtain the information from the discoveryresponse message to discover discoveree V2X UE. If the validity timer isexpired, the discoverer V2X UE may send a new discovery request messagetowards the HPLMN V2X function.

The flow diagram in the example embodiment in FIG. 30 shows an exampleprocedure for the match report. The procedure for match report fordiscoveree/discoverer comprises if the discoverer V2X UE may have overthe air received a V2X response code is matching the discovery responsefilter obtained in the discovery response message from the HPLMN V2Xfunction but the discoveree V2X UE may not have an RPAUID with a validTTL, the discoverer V2X UE may construct a match report messagecomprising its own RPAUID, its IMSI or MSISDN as UE identity, discoverytype set to “restricted discovery”, application ID set to uniqueidentifier for the application that may have triggered the monitoringrequest, the over the air received V2X response code, optional metadatarequested, and discoveree PLMN ID of the PLMN where the discoveree V2XUE may have been discovered. The discoveree V2X UE may transmit thematch report message towards the HPLMN V2X function.

The HPLMN V2X function may verify if the discoverer V2X UE may performrestricted discovery and may analyze V2X response code. The HPLMN V2Xfunction may identify the discoveree V2X UE's RPAUID in the context ofthe discoverer V2X UE.

If metadata requested was included to the originated match reportmessage by the discoverer V2X UE, the HPLMN V2X function may locate theV2X application server from the application ID and may construct anauthorization request message comprising discoverer V2X UE's RPAUID,discoveree V2X UE's RPAUID, and request type set to “restricteddiscovery/match”. The HPLMN V2X function may send the authorizationrequest message towards the V2X application server. This step isoptional if metadata requested was not included into the original matchreport message.

The V2X application server may construct an authorization responsecomprising discoverer V2X UE's PDUID, discoveree V2X UE's PDUID,response type set to “restricted discovery/match ack”, and metadatacorresponding to the discoveree V2X UE.

The HPLMN V2X function may verify that the PDUID may belong to thediscoverer V2X UE and the discoveree V2X UE's PDUID are the same as thediscoveree V2X UE's PDUID that may be stored in the context of thediscoverer V2X UE.

The HPLMN V2X function may construct a match report ack comprisingapplication ID set to unique identifier for the application that mayhave triggered the discovery request, discoveree V2X UE's RPAUID,validity timer, and optionally metadata.

The discoverer V2X UE may store the mapping between the V2X responsecode, discoveree V2X UE's PRAUID, the application ID unique identifierof the application that may have triggered the discovery procedure, andthe related validity timer.

The HPLMN V2X function may construct a match report info messagecomprising discoverer V2X UE's RPAUID, discoveree V2X UE's RPAUID,discoveree V2X UE's identity set to IMSI or MSISDN for chargingpurposes, V2X response code, and discovery type set to “restricteddiscovery”. The HPLMN V2X function may send the match report infomessage towards the discoveree V2X UE's PLMN V2X function and the V2Xfunction of the PLMN where the discoveree V2X UE may be roaming in.

Upon completion of the V2X group member discovery, the V2X group membersmay want to setup a V2X group call. In many situations, not all the V2Xgroup members have visibility for each other. Most of the time, the V2Xgroup members may not be visible by other members. Even if the V2X groupmembers may be visible to each other at one point, the visibility maychange due to e.g. movement of the V2X group members. In an exampleembodiment, in FIG. 31 V2X UE 1 sees V2X UE 2, V2X UE 3, V2X UE 4; V2XUE 2 sees V2X UE 1, V2X UE 3, V2X UE 4; V2X UE 3 sees V2X UE 1, V2X UE2, V2X UE 4; and V2X UE 4 sees V2X UE 1, V2X UE 2, V2X UE 3. Thisconfiguration may be shown the example embodiment of FIG. 32, wherenumber “1” may indicate visibility.

In one example embodiment, due to the possible e.g. movements of the V2Xgroup members, the positions of the V2X group members may change fromFIG. 31 to the example in FIG. 33, where V2X UE 1 sees V2X UE 2; V2X UE2 sees V2X UE 3 and V2X UE 4; V2X UE 3 sees V2X UE 2 and V2X UE 4; andV2X UE 4 sees V2X UE 3.

This configuration may be shown in an example embodiment, in FIG. 34,where “1” may show the visibility while “0” may show lack of visibility.The V2X group members who may be in a full communication as shown in theexample in FIG. 31, may lose visibility of other V2X members e.g. V2X UE1 and V2X UE 4 as shown in FIG. 33. This may happen due to the movementof the V2X members or other reasons e.g. geographic patterns, location.

In one example embodiment, the V2X group members may be aware of eachother's visibility with other word they may know the neighbors'neighbors. See the flow diagram in FIG. 35 exemplifying when V2X UE 2 inFIG. 33 distributes media within the V2X group. If V2X UE 2 distributesmedia, V2X UE 1 and V2X UE 3 may receive that media. If V2X UE 1 knowsthat V2X UE 2 has far better visibility than itself (since V2X UE 3 maybe visible to V2X UE 2 while not V2X UE 1), then it may realize there isno point to redistribute the media. If V2X UE 3 knows that it may havevisibility for V2X UE 4 while V2X UE 2 does not, it may realize that itmay need to redistribute the media. V2X UE 2 and V2X UE 4 may receivethe media if the media is redistributed by V2X UE 3. V2X UE 2 mayrecognize the media by e.g. tag and may ignore it for being repetitive.V2X UE 4 may know that V2X UE 3 has better visibility than itself (sinceV2X UE 3 may see V2X UE 2 while V2X UE 4 may not see V2X UE 2), it mayrealize it may not need to redistribute the media.

The exemplified configuration in FIG. 36 may illustrate the scenario inFIG. 33 where the numbering on the arrows may show the order of themedia distribution by V2X UE 2 and media redistribution by V2X UE 3.

In an example embodiment, as shown in FIG. 37, the steps of V2X memberdiscovery may be described. The actions in FIG. 37 may describe theprocedure of discovery new V2X group members and adding those to theneighboring list. Does the V2X group member discover a new member? Ifnot, then the V2X group member keeps looking until it finds a new V2Xgroup member, once the V2X group member finds another V2X group member,it adds that discovered member into its neighboring list, and the V2Xgroup member announces its neighboring list to other V2X group members.The last step in the flow chart is the announcement of the neighboringlist may be periodic and independent of the discovery of any new V2Xgroup members as shown in FIG. 38.

In one example embodiment, the flow chart in FIG. 39 shows the procedureof receiving the Neighboring List announcement by a V2X group member.The example in FIG. 39 shows upon receipt of the announcement of the V2Xneighboring list, the recipient checks if the received neighboring listis the same as the local neighboring list, if the answer is “YES”, noaction will be taken, and if the answer is “NO”, the local neighboringlist will be modified accordingly.

The above solution may not be applicable when there may exist adisconnect among some of the V2X group members. In an example embodimentas shown in FIG. 40, where V2X UE 1 discovers V2X UE 2; V2X UE 2discovers V2X UE 1; V2X UE 3 discovers none; and V2X UE 4 discoversnone, with the simplified configuration shown in FIG. 41.

If V2X UE 2 distributes media, it may only be heard by V2X UE 1 due tothe existing disconnect between V2X UE3, V2X UE 4 from V2X UE 1 and V2XUE 2. In the example embodiment shown in FIG. 42, V2X UE 2 may generatemedia which may be received by V2X UE 2 and the local neighboring listof V2X UE 2 contains V2X UE 1 and therefore V2X UE 2 will notre-distribute the media.

The configuration in FIG. 43 illustrates the above scenario where thenumbering on the arrows shows there won't be any redistribution.Therefore, the V2X group call cannot be established among all the V2Xgroup members. In Model A, if the discovery is not restricted, theannounced temp ID in FIG. 22 comprises V2X application code or V2Xapplication code prefix with V2X application code suffix(es) if theapplication-controlled extension is used, or if the discovery isrestricted, the announced temp ID in FIG. 22 comprises V2X restrictedcode or V2X restricted code prefix with V2X restricted code suffix(es)if the application-controlled extension is used.

In Model B the announced temp ID in FIG. 22 comprises V2X query code orV2X response code. The length of the announced temp ID may be 160 bitsand it comprises currently information about the V2X group ID and V2Xuser ID. In an example embodiment, to announce the neighboring list tothe V2X group neighbors may be to process the announced temp ID of theV2X discovery message with neighboring list and the required parametersfor the V2X discovery message and distributing the result over PC5interface as exemplified in FIG. 44.

FIG. 44 may show that the V2X discovery message and the neighboring listmay be processed into a V2X discovery message comprising the neighboringlist information. If the size of neighboring information is larger thanthe payload of the V2X discovery message, then neighboring list may bedivided into segments which individually gets processed by V2X discoverymessage. The transmitting V2X UE transmits the V2X discovery messagesover PC5 interface.

In the example embodiment FIG. 45, it is shown how the recipient V2X UEsmay receive the V2X discovery message with the neighboring listinformation which may be in segments. Having reverse processed the V2Xdiscovery message, the recipient V2X UE may parse the neighboring listor its segments from reversed processed V2X discovery message. If theneighboring list is in segments, the recipient V2X UE may collect thesegments from several received V2X discover messages to reconstruct theneighboring list belonging to the transmitting V2X UE.

In an example embodiment, if the discovery is restricted in Model A, theannouncing V2X UE may retrieve the PDUID and may provide it to the V2Xapplication server. The V2X application server may allocate RPAUID forPDUID which have been provided by that V2X UE. The announcing V2X UE mayuse the obtained RPAUID instead of PDUID. The V2X application server maystore the binding between the PDUID and RPAUID.

In an example embodiment, if the discovery is not restricted in Model A,the HPLMN V2X function may obtain V2X application ID from the announcingV2X UE and may provide V2X application code for that V2X application IDto that V2X UE. The V2X application code may be expired after a certainamount of time. In an example embodiment, if the discovery is restrictedin Model A, the HPLMN V2X function may obtain RPAUID from the announcingV2X UE and may provide V2X restricted code for that RPAUID to that V2XUE. The V2X restricted code may be expired after a certain amount oftime. In an example embodiment, if the discovery is not restricted inModel A, the HPLMN V2X function obtains V2X application ID from theannouncing V2X UE and may provide V2X application code prefix with V2Xapplication code suffix for that RPAUID to the V2X UE. The V2Xapplication code prefix with V2X application code suffix may be expiredafter a certain amount of time. In an example embodiment, if thediscovery is restricted in Model A, the HPLMN V2X function obtainsRPAUID from the announcing V2X UE and may provide V2X restricted codeprefix with V2X restricted code suffix for that RPAUID to the V2X UE.The V2X restricted code prefix with V2X restricted code suffix may beexpired after a certain amount of time. In an example embodiment, if thediscovery is not restricted in Model A, the HPLMN V2X function mayobtain V2X application ID from the announcing V2X UE and may provide V2Xapplication code prefix with V2X application code suffixes for that V2Xapplication ID to the V2X UE. The V2X application code prefix with V2Xapplication code suffixes may be expired after a certain amount of time.

In an example embodiment, if the discovery is restricted in Model A, theHPLMN V2X function may obtain RPAUID from the announcing V2X UE and mayprovide V2X restricted code prefix with V2X restricted code suffixes forthat RPAUID to the V2X UE. The V2X restricted code prefix with V2Xrestricted code suffixes may be expired after a certain amount of time.In an example embodiment, if the discovery is not restricted in Model A,the V2X UE may use V2X application code to announce its identity overPC5 interface. In an example embodiment, if the discovery is restrictedin Model A, the V2X UE may use V2X restricted code to announce itsidentity over PC5 interface. In an example embodiment, if the discoveryis not restricted in Model A, the V2X UE may use V2X application codeprefix and V2X application code suffix/V2X application code suffixes toannounce its identity over PC5 interface. In an example embodiment, ifthe discovery is restricted in Model A, the V2X UE may use V2Xrestricted code prefix and V2X restricted code suffix/V2X restrictedcode suffixes to announce its identity over PC5 interface. In an exampleembodiment, if the discovery is not restricted in Model A, the V2X UEmay use V2X application code to announce its neighboring list to the V2Xgroup neighbors over PC5 interface. In an example embodiment, if thediscovery is restricted in Model A, the V2X UE may use V2X restrictedcode to announce its neighboring list to the V2X group neighbors overPC5 interface. In an example embodiment, if the discovery is notrestricted in Model A, the V2X UE may use V2X application code toannounce one or more segments of its neighboring list to the V2X groupneighbors over PC5 interface. In an example embodiment, if the discoveryis restricted in Model A, the V2X UE may use V2X restricted code toannounce one or more segments of its neighboring list to the V2X groupneighbors over PC5 interface. In an example embodiment, if the discoveryis not restricted in Model A, the V2X UE may use V2X restricted codeprefix and V2X restricted code suffix/V2X restricted code suffixes toannounce its neighboring list to the V2X group neighbors over PC5interface. In an example embodiment, if the discovery is restricted inModel A, the V2X UE may use V2X restricted code prefix and V2Xrestricted code suffix/V2X restricted code suffixes to announce itsneighboring list to the V2X group neighbors over PC5 interface. In anexample embodiment, if the discovery is not restricted in Model A, theV2X UE may use V2X application code prefix and V2X application codesuffix/V2X application code suffixes to announce one or more segmentsits neighboring list to the V2X group neighbors over PC5 interface. Inan example embodiment, if the discovery is restricted in Model A, theV2X UE may use V2X restricted code prefix and V2X restricted codesuffix/V2X restricted code suffixes to announce one or more segments itsneighboring list to the V2X group neighbors over PC5 interface. Inexample embodiment if the discovery is not restricted in Model A, theannouncing V2X UE may be configured with V2X application ID.

In an example embodiment, if the discovery is restricted in Model A, theannouncing V2X UE may retrieve the PDUID and may provide it to the V2Xapplication server. The V2X application server may allocate RPAUID forPDUID which have been provided by that V2X UE. The announcing V2X UE mayuse the obtained RPAUID instead of PDUID. The V2X application server maystore the binding between the PDUID and RPAUID.

In an example embodiment, if the discovery is not restricted in Model A,the HPLMN V2X function may obtain V2X application ID from the announcingV2X UE and may provide container A for that V2X application ID to thatV2X UE. Container A may be expired after a certain amount of time. In anexample embodiment, if the discovery is restricted in Model A, the HPLMNV2X function may obtain RPAUID from the announcing V2X UE and mayprovide container A for that RPAUID to that V2X UE. Container A may beexpired after a certain amount of time.

In an example embodiment, if the discovery is not restricted container Amay be V2X application code and/or V2X application code prefix with V2Xapplication code suffix(es). In an example embodiment, if the discoveryis restricted container A may be V2X restricted code and/or V2Xrestricted code prefix with V2X restricted code suffix(es). In anexample embodiment, in Model A, the V2X UE may use container A toannounce its identity over PC5 interface. In an example embodiment, inModel A, the V2X UE may use container A to announce its neighboring listto the V2X group neighbors over PC5 interface. In an example embodiment,in Model A, the V2X UE may use container A to announce one or moresegment(s) of its neighboring list to the V2X group neighbors over PC5interface.

In one example embodiment, if the discovery is not restricted in theModel A, the V2X application ID of the announcing V2X UE may comprisethe vehicle type of the V2X UE. In one example embodiment, if thediscovery is not restricted in the Model A, the V2X application ID ofthe announcing V2X UE may comprise the pedestrian type of the V2X UE. Inone example embodiment, if the discovery is not restricted in the ModelA, the V2X application ID of the announcing V2X UE may comprise theinfrastructure type of the V2X UE. In one example embodiment, if thediscovery is not restricted in the Model A, the V2X application ID ofthe announcing V2X UE may comprise the vehicle-to-vehicle type of theV2X UE. In one example embodiment, if the discovery is not restricted inthe Model A, the V2X application ID of the announcing V2X UE maycomprise the vehicle-to-pedestrian type of the V2X UE. In one exampleembodiment, if the discovery is not restricted in the Model A, the V2Xapplication ID of the announcing V2X UE may comprise thevehicle-to-infrastructure type of the V2X UE. In one example embodiment,if the discovery is not restricted in the Model A, the V2X applicationID of the announcing V2X UE may comprise the vehicle-to-network type ofthe V2X UE.

In one example embodiment, if the discovery is not restricted in theModel A, the V2X application ID of the announcing V2X UE may comprise atleast two or more of the pedestrian type, vehicle type, infrastructuretype, vehicle-to-vehicle type, vehicle-to-pedestrian type,vehicle-to-infrastructure type, and/or vehicle-to-network type of theV2X UE. In one example embodiment, if the discovery is not restricted inthe Model A, the V2X application ID of the announcing V2X UE maycomprise all of the pedestrian type, vehicle type, infrastructure type,vehicle-to-vehicle type, vehicle-to-pedestrian type,vehicle-to-infrastructure type, and vehicle-to-network type of the V2XUE.

In one example embodiment, if the discovery is not restricted in theModel A, the V2X application ID of the announcing V2X UE may comprisethe emergency vehicle type of the V2X UE. In one example embodiment, ifthe discovery is not restricted in the Model A, the V2X application IDof the announcing V2X UE may comprise the emergency pedestrian type ofthe V2X UE. In one example embodiment, if the discovery is notrestricted in the Model A, the V2X application ID of the announcing V2XUE may comprise the emergency infrastructure type of the V2X UE. In oneexample embodiment, if the discovery is not restricted in the Model A,the V2X application ID of the announcing V2X UE may comprise theemergency vehicle-to-vehicle type of the V2X UE. In one exampleembodiment, if the discovery is not restricted in the Model A, the V2Xapplication ID of the announcing V2X UE may comprise the emergencyvehicle-to-pedestrian type of the V2X UE. In one example embodiment, ifthe discovery is not restricted in the Model A, the V2X application IDof the announcing V2X UE may comprise the emergencyvehicle-to-infrastructure type of the V2X UE. In one example embodiment,if the discovery is not restricted in the Model A, the V2X applicationID of the announcing V2X UE may comprise the emergencyvehicle-to-network type of the V2X UE.

In one example embodiment, if the discovery is not restricted in theModel A, the V2X application ID of the announcing V2X UE may comprise atleast two or more of the emergency pedestrian type, emergency vehicletype, emergency infrastructure type, emergency vehicle-to-vehicle type,emergency vehicle-to-pedestrian type, emergencyvehicle-to-infrastructure type, and/or emergency vehicle-to-network typeof the V2X UE. In one example embodiment, if the discovery is notrestricted in the Model A, the V2X application ID of the announcing V2XUE may comprise all of the emergency pedestrian type, emergency vehicletype, emergency infrastructure type, emergency vehicle-to-vehicle type,emergency vehicle-to-pedestrian type, emergencyvehicle-to-infrastructure type, and emergency vehicle-to-network type ofthe V2X UE.

In one example embodiment, if the discovery is restricted in the ModelA, the RPAUID which may be assigned to V2X discovery UE ID (PDUID) ofthe announcing V2X UE may comprise the vehicle type of the V2X UE. Inone example embodiment, if the discovery is restricted in the Model A,the RPAUID which may be assigned to V2X discovery UE ID (PDUID) of theannouncing V2X UE may comprise the pedestrian type of the V2X UE. In oneexample embodiment, if the discovery is restricted in the Model A, theRPAUID which may be assigned to V2X discovery UE ID (PDUID) of theannouncing V2X UE may comprise the infrastructure type of the V2X UE. Inone example embodiment, if the discovery is restricted in the Model A,the RPAUID which may be assigned to V2X discovery UE ID (PDUID) of theannouncing V2X UE may comprise the vehicle-to-vehicle type of the V2XUE. In one example embodiment, if the discovery is restricted in theModel A, the RPAUID which may be assigned to V2X discovery UE ID (PDUID)of the announcing V2X UE may comprise the vehicle-to-pedestrian type ofthe V2X UE. In one example embodiment, if the discovery is restricted inthe Model A, the RPAUID which may be assigned to V2X discovery UE ID(PDUID) of the announcing V2X UE may comprise thevehicle-to-infrastructure type of the V2X UE. In one example embodiment,if the discovery is restricted in the Model A, the RPAUID which may beassigned to V2X discovery UE ID (PDUID) of the announcing V2X UE maycomprise the vehicle-to-network type of the V2X UE.

In one example embodiment, if the discovery is restricted in the ModelA, the RPAUID which may be assigned to V2X discovery UE ID (PDUID) ofthe announcing V2X UE may comprise at least two or more of thepedestrian type, vehicle type, infrastructure type, vehicle-to-vehicletype, vehicle-to-pedestrian type, vehicle-to-infrastructure type, and/orvehicle-to-network type of the V2X UE. In one example embodiment, if thediscovery is restricted in the Model A, the RPAUID which may be assignedto V2X discovery UE ID (PDUID) of the announcing V2X UE may comprise allof the pedestrian type, vehicle type, infrastructure type,vehicle-to-vehicle type, vehicle-to-pedestrian type,vehicle-to-infrastructure type, and vehicle-to-network type of the V2XUE.

In one example embodiment, if the discovery is restricted in the ModelA, the RPAUID which may be assigned to V2X discovery UE ID (PDUID) ofthe announcing V2X UE may comprise the emergency vehicle type of the V2XUE. In one example embodiment, if the discovery is restricted in theModel A, the RPAUID which may be assigned to V2X discovery UE ID (PDUID)of the announcing V2X UE may comprise the emergency pedestrian type ofthe V2X UE. In one example embodiment, if the discovery is restricted inthe Model A, the RPAUID which may be assigned to V2X discovery UE ID(PDUID) of the announcing V2X UE may comprise the emergencyinfrastructure type of the V2X UE. In one example embodiment, if thediscovery is restricted in the Model A, the RPAUID which may be assignedto V2X discovery UE ID (PDUID) of the announcing V2X UE may comprise theemergency vehicle-to-vehicle type of the V2X UE. In one exampleembodiment, if the discovery is restricted in the Model A, the RPAUIDwhich may be assigned to V2X discovery UE ID (PDUID) of the announcingV2X UE may comprise the emergency vehicle-to-pedestrian type of the V2XUE. In one example embodiment, if the discovery is restricted in theModel A, the RPAUID which may be assigned to V2X discovery UE ID (PDUID)of the announcing V2X UE may comprise the emergencyvehicle-to-infrastructure type of the V2X UE. In one example embodiment,if the discovery is restricted in the Model A, the RPAUID which may beassigned to V2X discovery UE ID (PDUID) of the announcing V2X UE maycomprise the emergency vehicle-to-network type of the V2X UE.

In one example embodiment, if the discovery is restricted in the ModelA, the RPAUID which may be assigned to V2X discovery UE ID (PDUID) ofthe announcing V2X UE may comprise at least two or more of the emergencypedestrian type, emergency vehicle type, emergency infrastructure type,emergency vehicle-to-vehicle type, emergency vehicle-to-pedestrian type,emergency vehicle-to-infrastructure type, and/or emergencyvehicle-to-network type of the V2X UE. In one example embodiment, if thediscovery is restricted in the Model A, the RPAUID which may be assignedto V2X discovery UE ID (PDUID) of the announcing V2X UE may comprise allof the emergency pedestrian type, vehicle type, emergency infrastructuretype, emergency vehicle-to-vehicle type, emergency vehicle-to-pedestriantype, emergency vehicle-to-infrastructure type, and vehicle-to-networktype of the V2X UE.

In an example embodiment, if it is restricted discovery in Model A, themonitoring V2X UE may retrieve the PDUID and may provide it to the V2Xapplication server. The V2X application server may allocate RPAUID forPDUID which have been provided by that V2X UE. The monitoring V2X UE mayuse the obtained RPAUID instead of PDUID. The V2X application server maystore the binding between the PDUID and RPAUID.

In an example embodiment, if it is not restricted discovery in Model A,the HPLMN V2X function may obtain V2X application ID from the monitoringV2X UE and may provide discovery filter which may match V2X applicationcode for that V2X application ID of the announcing V2X UE. The HPLMN V2Xfunction may provide a time indicator for the expiration of the V2Xapplication code for that V2X application ID of the announcing V2X UE.

In an example embodiment, if it is restricted discovery in Model A, theHPLMN V2X function may obtain RPAUID from the monitoring V2X UE and mayprovide discovery filter which may match V2X restricted code for thatRPAUID of the announcing V2X UE. The HPLMN V2X function may provide atime indicator for the expiration of the V2X restricted code for thatRPAUID of the announcing V2X UE.

In an example embodiment, if the discovery is not restricted in Model A,the HPLMN V2X function may obtain V2X application ID from the monitoringV2X UE and may provide discovery filter which may match V2X applicationcode Prefix with V2X application code suffix for that V2X application IDof the announcing V2X UE. The HPLMN V2X function may provide a timeindicator for the expiration of the V2X application code Prefix with V2Xapplication code suffix for that V2X application ID of the announcingV2X UE.

In an example embodiment, if the discovery is restricted in Model A, theHPLMN V2X function may obtain RPAUID from the monitoring V2X UE and mayprovide discovery filter which may match V2X restricted code Prefix withV2X restricted code suffix for that RPAUID of the announcing V2X UE. TheHPLMN V2X function may provide a time indicator for the expiration ofthe V2X restricted code Prefix with V2X restricted code suffix for thatRPAUID of the announcing V2X UE.

In an example embodiment, if the discovery is not restricted in Model A,the HPLMN V2X function obtains V2X application ID from the monitoringV2X UE and may provide discovery filter which may match V2X applicationcode Prefix with V2X application code suffixes for that V2X applicationID of the announcing V2X UE. The HPLMN V2X function may provide a timeindicator for the expiration of the V2X application code Prefix with V2Xapplication code suffixes for that V2X application ID of the announcingV2X UE.

In an example embodiment, if the discovery is restricted in Model A, theHPLMN V2X function obtains RPAUID from the monitoring V2X UE and mayprovide discovery filter which may match V2X restricted code Prefix withV2X restricted code suffixes for that RPAUID of the announcing V2X UE.The HPLMN V2X function may provide a time indicator for the expirationof the V2X restricted code Prefix with V2X restricted code suffixes forthat RPAUID of the announcing V2X UE.

In an example embodiment, if the discovery is not restricted in Model Athe discovery filter of that monitoring V2X UE which may match V2Xapplication code indicates announcing UE's neighboring list to the V2Xgroup neighbors. In an example embodiment, if the discovery isrestricted in Model A the discovery filter of that monitoring V2X UEwhich may match V2X restricted code indicates announcing UE'sneighboring list to the V2X group neighbors. In an example embodiment,if the discovery is not restricted in Model A the discovery filter ofthat monitoring V2X UE which may match V2X application code prefix withV2X application code suffixes indicates announcing UE's neighboring listto the V2X group neighbors. In an example embodiment, if the discoveryis restricted in Model A the discovery filter of that monitoring V2X UEwhich may match V2X restricted code prefix with V2X restricted codesuffixes indicates announcing UE's neighboring list to the V2X groupneighbors. In example embodiment if the discovery is not restricted inModel A, the monitoring V2X UE may be configured with V2X applicationID.

In an example embodiment, if the discovery is restricted in Model A themonitoring V2X UE may retrieve the PDUID and may provide it to the V2Xapplication server. The V2X application server may allocate RPAUID forPDUID which have been provided by that V2X UE. The monitoring V2X UE mayuse the obtained RPAUID instead of PDUID. The V2X application server maystore the binding between the PDUID and RPAUID.

In an example embodiment, if the discovery is not restricted in Model A,the HPLMN V2X function may obtain V2X application ID from the monitoringV2X UE and may provide container A which may match container B for thatV2X application ID of the announcing V2X UE. The HPLMN V2X function mayprovide a time indicator for the expiration of the container B for thatV2X application ID of the announcing V2X UE.

In an example embodiment, if the discovery is restricted in Model A, theHPLMN V2X function may obtain RPAUID from the monitoring V2X UE and mayprovide container A which may match container B for that RPAUID of theannouncing V2X UE. The HPLMN V2X function may provide a time indicatorfor the expiration of the container B for that RPAUID of the announcingV2X UE.

In an example embodiment, if the discovery is not restricted in Model Acontainer A of that monitoring V2X UE which may match container Bindicates announcing UE's neighboring list to the V2X group neighbors.In one example embodiment, container A may be discovery filter. In oneexample embodiment, container B may be V2X application code and/or V2Xapplication code Prefix with V2X application code suffix(es).

In an example embodiment, if the discovery is restricted in Model Acontainer A of that monitoring V2X UE which may match container Bindicates announcing UE's neighboring list to the V2X group neighbors.In one example embodiment, container A may be discovery filter. In oneexample embodiment, container B may be V2X restricted code and/or V2Xrestricted code Prefix with V2X restricted code suffix(es).

In one example embodiment, if the discovery is not restricted in theModel A, the discovery filter of the monitoring V2X UE which may matchV2X application code for that V2X application ID of the announcing V2Xmay identify the vehicle type of the announcing V2X UE. In one exampleembodiment, if the discovery is not restricted in the Model A, thediscovery filter of the monitoring V2X UE which may match V2Xapplication code for that V2X application ID of the announcing V2X mayidentify the pedestrian type of the announcing V2X UE. In one exampleembodiment, if the discovery is not restricted in the Model A, thediscovery filter of the monitoring V2X UE which may match V2Xapplication code for that V2X application ID of the announcing V2X mayidentify the infrastructure type of the announcing V2X UE. In oneexample embodiment, if the discovery is not restricted in the Model A,the discovery filter of the monitoring V2X UE which may match V2Xapplication code for that V2X application ID of the announcing V2X mayidentify the vehicle-to-vehicle type of the announcing V2X UE. In oneexample embodiment, if the discovery is not restricted in the Model A,the discovery filter of the monitoring V2X UE which may match V2Xapplication code for that V2X application ID of the announcing V2X mayidentify the vehicle-to-pedestrian type of the announcing V2X UE. In oneexample embodiment, if the discovery is not restricted in the Model A,the discovery filter of the monitoring V2X UE which may match V2Xapplication code for that V2X application ID of the announcing V2X mayidentify the vehicle-to-infrastructure type of the announcing V2X UE. Inone example embodiment, if the discovery is not restricted in the ModelA, the discovery filter of the monitoring V2X UE which may match V2Xapplication code for that V2X application ID of the announcing V2X mayidentify the vehicle-to-network type of the announcing V2X UE.

In one example embodiment, if the discovery is not restricted in theModel A, the discovery filter of the monitoring V2X UE which may matchV2X application code for that V2X application ID of the announcing V2Xmay identify at least two or more of the pedestrian type, the vehicletype, the infrastructure type, vehicle-to-vehicle type,vehicle-to-pedestrian type, vehicle-to-network, and/or vehicle-toinfrastructure type of the announcing V2X UE. In one example embodiment,if the discovery is not restricted in the Model A, the discovery filterof the monitoring V2X UE which may match V2X application code for thatV2X application ID of the announcing V2X may identify all of thepedestrian type, the vehicle type, the infrastructure type,vehicle-to-vehicle type, vehicle-to-pedestrian type, vehicle-to-network,and vehicle-to infrastructure type of the announcing V2X UE.

In one example embodiment, if the discovery is not restricted in theModel A, the discovery filter of the monitoring V2X UE which may matchV2X application code prefix with V2X application code suffix(es) forthat V2X application ID of the announcing V2X may identify the vehicletype of the announcing V2X UE. In one example embodiment, if thediscovery is not restricted in the Model A, the discovery filter of themonitoring V2X UE which may match V2X application code prefix with V2Xapplication code suffix(es) for that V2X application ID of theannouncing V2X may identify the pedestrian type of the announcing V2XUE.

In one example embodiment, if the discovery is not restricted in theModel A, the discovery filter of the monitoring V2X UE which may matchV2X application code prefix with V2X application code suffix(es) forthat V2X application ID of the announcing V2X may identify theinfrastructure type of the announcing V2X UE. In one example embodiment,if the discovery is not restricted in the Model A, the discovery filterof the monitoring V2X UE which may match V2X application code prefixwith V2X application code suffix(es) for that V2X application ID of theannouncing V2X may identify the vehicle-to-vehicle type of theannouncing V2X UE. In one example embodiment, if the discovery is notrestricted in the Model A, the discovery filter of the monitoring V2X UEwhich may match V2X application code prefix with V2X application codesuffix(es) for that V2X application ID of the announcing V2X mayidentify the vehicle-to-network type of the announcing V2X UE. In oneexample embodiment, if the discovery is not restricted in the Model A,the discovery filter of the monitoring V2X UE which may match V2Xapplication code prefix with V2X application code suffix(es) for thatV2X application ID of the announcing V2X may identify thevehicle-to-pedestrian type of the announcing V2X UE. In one exampleembodiment, if the discovery is not restricted in the Model A, thediscovery filter of the monitoring V2X UE which may match V2Xapplication code prefix with V2X application code suffix(es) for thatV2X application ID of the announcing V2X may identify thevehicle-to-infrastructure type of the announcing V2X UE.

In one example embodiment, if the discovery is not restricted in theModel A, the discovery filter of the monitoring V2X UE which may matchV2X application code prefix with V2X application code suffix(es) forthat V2X application ID of the announcing V2X may identify at least twoor more of the pedestrian type, the vehicle type, or the infrastructuretype, vehicle-to-vehicle type, vehicle-to-pedestrian type,vehicle-to-network, and/or vehicle-to infrastructure type of theannouncing V2X UE. In one example embodiment, if the discovery is notrestricted in the Model A, the discovery filter of the monitoring V2X UEwhich may match V2X application code prefix with V2X application codesuffix(es) for that V2X application ID of the announcing V2X mayidentify all of the pedestrian type, the vehicle type, theinfrastructure type, vehicle-to-vehicle type, vehicle-to-pedestriantype, vehicle-to-network, and vehicle-to infrastructure type of theannouncing V2X UE.

In one example embodiment, if the discovery is restricted in the ModelA, the discovery filter of the monitoring V2X UE which may match V2Xrestricted code for the RPAUID which may have been assigned to V2Xdiscovery UE ID (PDUID) of the announcing V2X UE may comprise thevehicle type of the announcing V2X UE. In one example embodiment, if thediscovery is restricted in the Model A, the discovery filter of themonitoring V2X UE which may match V2X restricted code for the RPAUIDwhich may have been assigned to V2X discovery UE ID (PDUID) of theannouncing V2X UE may comprise the pedestrian type of the announcing V2XUE. In one example embodiment, if the discovery is restricted in theModel A, the discovery filter of the monitoring V2X UE which may matchV2X restricted code for the RPAUID which may have been assigned to V2Xdiscovery UE ID (PDUID) of the announcing V2X UE may comprise theinfrastructure type of the announcing V2X UE. In one example embodiment,if the discovery is restricted in the Model A, the discovery filter ofthe monitoring V2X UE which may match V2X restricted code for the RPAUIDwhich may have been assigned to V2X discovery UE ID (PDUID) of theannouncing V2X UE may comprise the vehicle-to-vehicle type of theannouncing V2X UE. In one example embodiment, if the discovery isrestricted in the Model A, the discovery filter of the monitoring V2X UEwhich may match V2X restricted code for the RPAUID which may have beenassigned to V2X discovery UE ID (PDUID) of the announcing V2X UE maycomprise the vehicle-to-pedestrian type of the announcing V2X UE. In oneexample embodiment, if the discovery is restricted in the Model A, thediscovery filter of the monitoring V2X UE which may match V2X restrictedcode for the RPAUID which may have been assigned to V2X discovery UE ID(PDUID) of the announcing V2X UE may comprise thevehicle-to-infrastructure type of the announcing V2X UE. In one exampleembodiment, if the discovery is restricted in the Model A, the discoveryfilter of the monitoring V2X UE which may match V2X restricted code forthe RPAUID which may have been assigned to V2X discovery UE ID (PDUID)of the announcing V2X UE may comprise the vehicle-to-network type of theannouncing V2X UE.

In one example embodiment, if the discovery is restricted in the ModelA, the discovery filter of the monitoring V2X UE which may match V2Xrestricted code for the RPAUID which may have been assigned to V2Xdiscovery UE ID (PDUID) of the announcing V2X UE may comprise at leasttwo or more of the pedestrian type, the vehicle type, the infrastructuretype, vehicle-to-vehicle type, vehicle-to-pedestrian type,vehicle-to-network, and/or vehicle-to infrastructure type of theannouncing V2X UE.

In one example embodiment, if the discovery is restricted in the ModelA, the discovery filter of the monitoring V2X UE which may match V2Xrestricted code for the RPAUID which may have been assigned to V2Xdiscovery UE ID (PDUID) of the announcing V2X UE may comprise all of thepedestrian type, the vehicle type, the infrastructure type,vehicle-to-vehicle type, vehicle-to-pedestrian type, vehicle-to-network,and vehicle-to infrastructure type of the announcing V2X UE.

In one example embodiment, if the discovery is restricted in the ModelA, the discovery filter of the monitoring V2X UE which may match V2Xrestricted code prefix with V2X restricted code suffix(es) for theRPAUID which may have been assigned to V2X discovery UE ID (PDUID) ofthe announcing V2X UE may comprise the vehicle type of the announcingV2X UE. In one example embodiment, if the discovery is restricted in theModel A, the discovery filter of the monitoring V2X UE which may matchV2X restricted code prefix with V2X restricted code suffix(es) for theRPAUID which may have been assigned to V2X discovery UE ID (PDUID) ofthe announcing V2X UE may comprise the pedestrian type of the announcingV2X UE.

In one example embodiment, if the discovery is restricted in the ModelA, the discovery filter of the monitoring V2X UE which may match V2Xrestricted code prefix with V2X restricted code suffix(es) for theRPAUID which may have been assigned to V2X discovery UE ID (PDUID) ofthe announcing V2X UE may comprise the infrastructure type of theannouncing V2X UE. In one example embodiment, if the discovery isrestricted in the Model A, the discovery filter of the monitoring V2X UEwhich may match V2X restricted code prefix with V2X restricted codesuffix(es) for the RPAUID which may have been assigned to V2X discoveryUE ID (PDUID) of the announcing V2X UE may comprise thevehicle-to-vehicle type of the announcing V2X UE.

In one example embodiment, if the discovery is restricted in the ModelA, the discovery filter of the monitoring V2X UE which may match V2Xrestricted code prefix with V2X restricted code suffix(es) for theRPAUID which may have been assigned to V2X discovery UE ID (PDUID) ofthe announcing V2X UE may comprise the vehicle-to-pedestrian type of theannouncing V2X UE. In one example embodiment, if the discovery isrestricted in the Model A, the discovery filter of the monitoring V2X UEwhich may match V2X restricted code prefix with V2X restricted codesuffix(es) for the RPAUID which may have been assigned to V2X discoveryUE ID (PDUID) of the announcing V2X UE may comprise thevehicle-to-infrastructure type of the announcing V2X UE. In one exampleembodiment, if the discovery is restricted in the Model A, the discoveryfilter of the monitoring V2X UE which may match V2X restricted codeprefix with V2X restricted code suffix(es) for the RPAUID which may havebeen assigned to V2X discovery UE ID (PDUID) of the announcing V2X UEmay comprise the vehicle-to-network type of the announcing V2X UE.

In one example embodiment, if the discovery is restricted in the ModelA, the discovery filter of the monitoring V2X UE which may match V2Xrestricted code prefix with V2X restricted code suffix(es) for theRPAUID which may have been assigned to V2X discovery UE ID (PDUID) ofthe announcing V2X UE may comprise at least two or more of thepedestrian type, the vehicle type, the infrastructure type,vehicle-to-vehicle type, vehicle-to-pedestrian type, vehicle-to-network,and/or vehicle-to-infrastructure type of the announcing V2X UE.

In one example embodiment, if the discovery is restricted in the ModelA, the discovery filter of the monitoring V2X UE which may match V2Xrestricted code prefix with V2X restricted code suffix(es) for theRPAUID which may have been assigned to V2X discovery UE ID (PDUID) ofthe announcing V2X UE may comprise all of the pedestrian type, thevehicle type, the infrastructure type, vehicle-to-vehicle type,vehicle-to-pedestrian type, vehicle-to-network, andvehicle-to-infrastructure type of the announcing V2X UE.

In one example embodiment, if the discovery is not restricted in theModel A, the discovery filter of the monitoring V2X UE which may matchV2X application code for that V2X application ID of the announcing V2Xmay identify the emergency vehicle type of the announcing V2X UE. In oneexample embodiment, if the discovery is not restricted in the Model A,the discovery filter of the monitoring V2X UE which may match V2Xapplication code for that V2X application ID of the announcing V2X mayidentify the emergency pedestrian type of the announcing V2X UE. In oneexample embodiment, if the discovery is not restricted in the Model A,the discovery filter of the monitoring V2X UE which may match V2Xapplication code for that V2X application ID of the announcing V2X mayidentify the emergency infrastructure type of the announcing V2X UE. Inone example embodiment, if the discovery is not restricted in the ModelA, the discovery filter of the monitoring V2X UE which may match V2Xapplication code for that V2X application ID of the announcing V2X mayidentify the emergency vehicle-to-vehicle type of the announcing V2X UE.In one example embodiment, if the discovery is not restricted in theModel A, the discovery filter of the monitoring V2X UE which may matchV2X application code for that V2X application ID of the announcing V2Xmay identify the emergency vehicle-to-pedestrian type of the announcingV2X UE. In one example embodiment, if the discovery is not restricted inthe Model A, the discovery filter of the monitoring V2X UE which maymatch V2X application code for that V2X application ID of the announcingV2X may identify the emergency vehicle-to-infrastructure type of theannouncing V2X UE. In one example embodiment, if the discovery is notrestricted in the Model A, the discovery filter of the monitoring V2X UEwhich may match V2X application code for that V2X application ID of theannouncing V2X may identify the emergency vehicle-to-network type of theannouncing V2X UE.

In one example embodiment, if the discovery is not restricted in theModel A, the discovery filter of the monitoring V2X UE which may matchV2X application code for that V2X application ID of the announcing V2Xmay identify at least two or more of the emergency pedestrian type, theemergency vehicle type, the emergency infrastructure type, emergencyvehicle-to-vehicle type, emergency vehicle-to-pedestrian type, emergencyvehicle-to-network, and/or emergency vehicle-to infrastructure type ofthe announcing V2X UE.

In one example embodiment, if the discovery is not restricted in theModel A, the discovery filter of the monitoring V2X UE which may matchV2X application code for that V2X application ID of the announcing V2Xmay identify all of the emergency pedestrian type, the emergency vehicletype, the emergency infrastructure type, emergency vehicle-to-vehicletype, emergency vehicle-to-pedestrian type, emergencyvehicle-to-network, and emergency vehicle-to infrastructure type of theannouncing V2X UE.

In one example embodiment, if the discovery is not restricted in theModel A, the discovery filter of the monitoring V2X UE which may matchV2X application code prefix with V2X application code suffix(es) forthat V2X application ID of the announcing V2X may identify the emergencyvehicle type of the announcing V2X UE. In one example embodiment, if thediscovery is not restricted in the Model A, the discovery filter of themonitoring V2X UE which may match V2X application code prefix with V2Xapplication code suffix(es) for that V2X application ID of theannouncing V2X may identify the emergency pedestrian type of theannouncing V2X UE. In one example embodiment, if the discovery is notrestricted in the Model A, the discovery filter of the monitoring V2X UEwhich may match V2X application code prefix with V2X application codesuffix(es) for that V2X application ID of the announcing V2X mayidentify the emergency infrastructure type of the announcing V2X UE. Inone example embodiment, if the discovery is not restricted in the ModelA, the discovery filter of the monitoring V2X UE which may match V2Xapplication code prefix with V2X application code suffix(es) for thatV2X application ID of the announcing V2X may identify the emergencyvehicle-to-vehicle type of the announcing V2X UE. In one exampleembodiment, if the discovery is not restricted in the Model A, thediscovery filter of the monitoring V2X UE which may match V2Xapplication code prefix with V2X application code suffix(es) for thatV2X application ID of the announcing V2X may identify the emergencyvehicle-to-network type of the announcing V2X UE. In one exampleembodiment, if the discovery is not restricted in the Model A, thediscovery filter of the monitoring V2X UE which may match V2Xapplication code prefix with V2X application code suffix(es) for thatV2X application ID of the announcing V2X may identify the emergencyvehicle-to-pedestrian type of the announcing V2X UE. In one exampleembodiment, if the discovery is not restricted in the Model A, thediscovery filter of the monitoring V2X UE which may match V2Xapplication code prefix with V2X application code suffix(es) for thatV2X application ID of the announcing V2X may identify the emergencyvehicle-to-infrastructure type of the announcing V2X UE.

In one example embodiment, if the discovery is not restricted in theModel A, the discovery filter of the monitoring V2X UE which may matchV2X application code prefix with V2X application code suffix(es) forthat V2X application ID of the announcing V2X may identify at least twoor more of the emergency pedestrian type, the emergency vehicle type, orthe emergency infrastructure type, emergency vehicle-to-vehicle type,emergency vehicle-to-pedestrian type, emergency vehicle-to-network,and/or emergency vehicle-to infrastructure type of the announcing V2XUE.

In one example embodiment, if the discovery is not restricted in theModel A, the discovery filter of the monitoring V2X UE which may matchV2X application code prefix with V2X application code suffix(es) forthat V2X application ID of the announcing V2X may identify all of theemergency pedestrian type, the emergency vehicle type, the emergencyinfrastructure type, emergency vehicle-to-vehicle type, emergencyvehicle-to-pedestrian type, emergency vehicle-to-network, and emergencyvehicle-to infrastructure type of the announcing V2X UE.

In one example embodiment, if the discovery is restricted in the ModelA, the discovery filter of the monitoring V2X UE which may match V2Xrestricted code for the RPAUID which may have been assigned to V2Xdiscovery UE ID (PDUID) of the announcing V2X UE may comprise theemergency vehicle type of the announcing V2X UE. In one exampleembodiment, if the discovery is restricted in the Model A, the discoveryfilter of the monitoring V2X UE which may match V2X restricted code forthe RPAUID which may have been assigned to V2X discovery UE ID (PDUID)of the announcing V2X UE may comprise the emergency pedestrian type ofthe announcing V2X UE. In one example embodiment, if the discovery isrestricted in the Model A, the discovery filter of the monitoring V2X UEwhich may match V2X restricted code for the RPAUID which may have beenassigned to V2X discovery UE ID (PDUID) of the announcing V2X UE maycomprise the emergency infrastructure type of the announcing V2X UE. Inone example embodiment, if the discovery is restricted in the Model A,the discovery filter of the monitoring V2X UE which may match V2Xrestricted code for the RPAUID which may have been assigned to V2Xdiscovery UE ID (PDUID) of the announcing V2X UE may comprise theemergency vehicle-to-vehicle type of the announcing V2X UE. In oneexample embodiment, if the discovery is restricted in the Model A, thediscovery filter of the monitoring V2X UE which may match V2X restrictedcode for the RPAUID which may have been assigned to V2X discovery UE ID(PDUID) of the announcing V2X UE may comprise the emergencyvehicle-to-pedestrian type of the announcing V2X UE.

In one example embodiment, if the discovery is restricted in the ModelA, the discovery filter of the monitoring V2X UE which may match V2Xrestricted code for the RPAUID which may have been assigned to V2Xdiscovery UE ID (PDUID) of the announcing V2X UE may comprise theemergency vehicle-to-infrastructure type of the announcing V2X UE. Inone example embodiment, if the discovery is restricted in the Model A,the discovery filter of the monitoring V2X UE which may match V2Xrestricted code for the RPAUID which may have been assigned to V2Xdiscovery UE ID (PDUID) of the announcing V2X UE may comprise theemergency vehicle-to-network type of the announcing V2X UE. In oneexample embodiment, if the discovery is restricted in the Model A, thediscovery filter of the monitoring V2X UE which may match V2X restrictedcode for the RPAUID which may have been assigned to V2X discovery UE ID(PDUID) of the announcing V2X UE may comprise at least two or more ofthe emergency pedestrian type, the emergency vehicle type, the emergencyinfrastructure type, emergency vehicle-to-vehicle type, emergencyvehicle-to-pedestrian type, emergency vehicle-to-network, and/oremergency vehicle-to infrastructure type of the announcing V2X UE.

In one example embodiment, if the discovery is restricted in the ModelA, the discovery filter of the monitoring V2X UE which may match V2Xrestricted code for the RPAUID which may have been assigned to V2Xdiscovery UE ID (PDUID) of the announcing V2X UE may comprise all of theemergency pedestrian type, the emergency vehicle type, the emergencyinfrastructure type, emergency vehicle-to-vehicle type, emergencyvehicle-to-pedestrian type, emergency vehicle-to-network, and emergencyvehicle-to infrastructure type of the announcing V2X UE.

In one example embodiment, if the discovery is restricted in the ModelA, the discovery filter of the monitoring V2X UE which may match V2Xrestricted code prefix with V2X restricted code suffix(es) for theRPAUID which may have been assigned to V2X discovery UE ID (PDUID) ofthe announcing V2X UE may comprise the emergency vehicle type of theannouncing V2X UE.

In one example embodiment, if the discovery is restricted in the ModelA, the discovery filter of the monitoring V2X UE which may match V2Xrestricted code prefix with V2X restricted code suffix(es) for theRPAUID which may have been assigned to V2X discovery UE ID (PDUID) ofthe announcing V2X UE may comprise the emergency pedestrian type of theannouncing V2X UE. In one example embodiment, if the discovery isrestricted in the Model A, the discovery filter of the monitoring V2X UEwhich may match V2X restricted code prefix with V2X restricted codesuffix(es) for the RPAUID which may have been assigned to V2X discoveryUE ID (PDUID) of the announcing V2X UE may comprise the emergencyinfrastructure type of the announcing V2X UE. In one example embodiment,if the discovery is restricted in the Model A, the discovery filter ofthe monitoring V2X UE which may match V2X restricted code prefix withV2X restricted code suffix(es) for the RPAUID which may have beenassigned to V2X discovery UE ID (PDUID) of the announcing V2X UE maycomprise the emergency vehicle-to-vehicle type of the announcing V2X UE.In one example embodiment, if the discovery is restricted in the ModelA, the discovery filter of the monitoring V2X UE which may match V2Xrestricted code prefix with V2X restricted code suffix(es) for theRPAUID which may have been assigned to V2X discovery UE ID (PDUID) ofthe announcing V2X UE may comprise the emergency vehicle-to-pedestriantype of the announcing V2X UE. In one example embodiment, if thediscovery is restricted in the Model A, the discovery filter of themonitoring V2X UE which may match V2X restricted code prefix with V2Xrestricted code suffix(es) for the RPAUID which may have been assignedto V2X discovery UE ID (PDUID) of the announcing V2X UE may comprise theemergency vehicle-to-infrastructure type of the announcing V2X UE. Inone example embodiment, if the discovery is restricted in the Model A,the discovery filter of the monitoring V2X UE which may match V2Xrestricted code prefix with V2X restricted code suffix(es) for theRPAUID which may have been assigned to V2X discovery UE ID (PDUID) ofthe announcing V2X UE may comprise the emergency vehicle-to-network typeof the announcing V2X UE.

In one example embodiment, if the discovery is restricted in the ModelA, the discovery filter of the monitoring V2X UE which may match V2Xrestricted code prefix with V2X restricted code suffix(es) for theRPAUID which may have been assigned to V2X discovery UE ID (PDUID) ofthe announcing V2X UE may comprise at least two or more of the emergencypedestrian type, the emergency vehicle type, the emergencyinfrastructure type, emergency vehicle-to-vehicle type, emergencyvehicle-to-pedestrian type, emergency vehicle-to-network, and/oremergency vehicle-to-infrastructure type of the announcing V2X UE.

In one example embodiment, if the discovery is restricted in the ModelA, the discovery filter of the monitoring V2X UE which may match V2Xrestricted code prefix with V2X restricted code suffix(es) for theRPAUID which may have been assigned to V2X discovery UE ID (PDUID) ofthe announcing V2X UE may comprise all of the emergency pedestrian type,the emergency vehicle type, the emergency infrastructure type, emergencyvehicle-to-vehicle type, emergency vehicle-to-pedestrian type, emergencyvehicle-to-network, and emergency vehicle-to-infrastructure type of theannouncing V2X UE.

In an example embodiment, in Model B the discoveree V2X UE may retrievethe PDUID and may provide it to the V2X application server. The V2Xapplication server may allocate RPAUID for PDUID which have beenprovided by that V2X UE. The discoveree V2X UE may use the obtainedRPAUID instead of PDUID. The V2X application server may store thebinding between the PDUID and RPAUID.

In an example embodiment, in Model B, the HPLMN V2X function may obtainRPAUID from the discoveree V2X UE and may provide V2X response code andV2X query filter matched for certain V2X query code for that RPAUID tothat V2X UE. The V2X response code and V2X query filter may be expiredafter a certain amount of time.

In an example embodiment, in Model B, the HPLMN V2X function obtainsRPAUID from the discoveree V2X UE and may provide V2X response code andV2X query filters matched for certain V2X query code for that RPAUID tothat V2X UE. The V2X response code and V2X query filters may be expiredafter a certain amount of time.

In an example embodiment, in Model B the discoveree V2X UE may use V2Xresponse code to response over interface PC5 to a received V2X querycode which may be matched to the V2X query filter. In an exampleembodiment, in Model B the discoveree V2X UE may use V2X response codeto response over interface PC5 to a received V2X query code which may bematched to one or more of the V2X query filters. In an exampleembodiment, in Model B the V2X response code and one or more V2X queryfilter(s) which may be matched to a V2X query code indicate discovereeUE's neighboring list to the V2X group neighbors. In an exampleembodiment, in Model B the V2X response code and one or more V2X queryfilter(s) which may be matched to a V2X query code indicate one or moresegment(s) of discoveree UE's neighboring list to the V2X groupneighbors.

In an example embodiment, in Model B the discoveree V2X UE may retrievethe PDUID and may provide it to the V2X application server. The V2Xapplication server may allocate RPAUID for PDUID which have beenprovided by that V2X UE. The discoveree V2X UE may use the obtainedRPAUID instead of PDUID. The V2X application server may store thebinding between the PDUID and RPAUID.

In one example embodiment, in the Model B, the V2X query filter of thediscoveree V2X UE which may match V2X query code for the RPAUID whichmay have been assigned to V2X discovery UE ID (PDUID) of the discovererV2X UE may comprise the vehicle type of the discoverer V2X UE. In oneexample embodiment, in the Model B, the V2X query filter of thediscoveree V2X UE which may match V2X query code for the RPAUID whichmay have been assigned to V2X discovery UE ID (PDUID) of the discovererV2X UE may comprise the pedestrian type of the discoverer V2X UE. In oneexample embodiment, in the Model B, the V2X query filter of thediscoveree V2X UE which may match V2X query code for the RPAUID whichmay have been assigned to V2X discovery UE ID (PDUID) of the discovererV2X UE may comprise the infrastructure type of the discoverer V2X UE. Inone example embodiment, in the Model B, the V2X query filter of thediscoveree V2X UE which may match V2X query code for the RPAUID whichmay have been assigned to V2X discovery UE ID (PDUID) of the discovererV2X UE may comprise the vehicle-to-vehicle type of the discoverer V2XUE. In one example embodiment, in the Model B, the V2X query filter ofthe discoveree V2X UE which may match V2X query code for the RPAUIDwhich may have been assigned to V2X discovery UE ID (PDUID) of thediscoverer V2X UE may comprise the vehicle-to-pedestrian type of thediscoverer V2X UE. In one example embodiment, in the Model B, the V2Xquery filter of the discoveree V2X UE which may match V2X query code forthe RPAUID which may have been assigned to V2X discovery UE ID (PDUID)of the discoverer V2X UE may comprise the vehicle-to-network type of thediscoverer V2X UE. In one example embodiment, in the Model B, the V2Xquery filter of the discoveree V2X UE which may match V2X query code forthe RPAUID which may have been assigned to V2X discovery UE ID (PDUID)of the discoverer V2X UE may comprise the vehicle-to-infrastructure typeof the discoverer V2X UE.

In one example embodiment, in the Model B, the V2X query filter of thediscoveree V2X UE which may match V2X query code for the RPAUID whichmay have been assigned to V2X discovery UE ID (PDUID) of the discovererV2X UE may comprise at least two or more of the pedestrian type, thevehicle type, the infrastructure type, vehicle-to-vehicle type,vehicle-to-pedestrian type, vehicle-to-network, and/orvehicle-to-infrastructure type of the discoverer V2X UE.

In one example embodiment, in the Model B, the V2X query filter of thediscoveree V2X UE which may match V2X query code for the RPAUID whichmay have been assigned to V2X discovery UE ID (PDUID) of the discovererV2X UE may comprise all of the pedestrian type, the vehicle type, theinfrastructure type, vehicle-to-vehicle type, vehicle-to-pedestriantype, vehicle-to-network, and vehicle-to-infrastructure type of thediscoverer V2X UE.

In one example embodiment, in the Model B, the V2X query filter of thediscoveree V2X UE which may match V2X query code for the RPAUID whichmay have been assigned to V2X discovery UE ID (PDUID) of the discovererV2X UE may comprise the emergency vehicle type of the discoverer V2X UE.In one example embodiment, in the Model B, the V2X query filter of thediscoveree V2X UE which may match V2X query code for the RPAUID whichmay have been assigned to V2X discovery UE ID (PDUID) of the discovererV2X UE may comprise the emergency pedestrian type of the discoverer V2XUE. In one example embodiment, in the Model B, the V2X query filter ofthe discoveree V2X UE which may match V2X query code for the RPAUIDwhich may have been assigned to V2X discovery UE ID (PDUID) of thediscoverer V2X UE may comprise the emergency infrastructure type of thediscoverer V2X UE. In one example embodiment, in the Model B, the V2Xquery filter of the discoveree V2X UE which may match V2X query code forthe RPAUID which may have been assigned to V2X discovery UE ID (PDUID)of the discoverer V2X UE may comprise the emergency vehicle-to-vehicletype of the discoverer V2X UE. In one example embodiment, in the ModelB, the V2X query filter of the discoveree V2X UE which may match V2Xquery code for the RPAUID which may have been assigned to V2X discoveryUE ID (PDUID) of the discoverer V2X UE may comprise the emergencyvehicle-to-pedestrian type of the discoverer V2X UE. In one exampleembodiment, in the Model B, the V2X query filter of the discoveree V2XUE which may match V2X query code for the RPAUID which may have beenassigned to V2X discovery UE ID (PDUID) of the discoverer V2X UE maycomprise the emergency vehicle-to-network type of the discoverer V2X UE.In one example embodiment, in the Model B, the V2X query filter of thediscoveree V2X UE which may match V2X query code for the RPAUID whichmay have been assigned to V2X discovery UE ID (PDUID) of the discovererV2X UE may comprise the emergency vehicle-to-infrastructure type of thediscoverer V2X UE.

In one example embodiment, in the Model B, the V2X query filter of thediscoveree V2X UE which may match V2X query code for the RPAUID whichmay have been assigned to V2X discovery UE ID (PDUID) of the discovererV2X UE may comprise at least two or more of the emergency pedestriantype, the emergency vehicle type, the emergency infrastructure type,emergency vehicle-to-vehicle type, emergency vehicle-to-pedestrian type,emergency vehicle-to-network, and/or emergency vehicle-to-infrastructuretype of the discoverer V2X UE.

In one example embodiment, in the Model B, the V2X query filter of thediscoveree V2X UE which may match V2X query code for the RPAUID whichmay have been assigned to V2X discovery UE ID (PDUID) of the discovererV2X UE may comprise all of the emergency pedestrian type, the emergencyvehicle type, the emergency infrastructure type, emergencyvehicle-to-vehicle type, emergency vehicle-to-pedestrian type, emergencyvehicle-to-network, and emergency vehicle-to-infrastructure type of thediscoverer V2X UE.

In an example embodiment, in Model B, the HPLMN V2X function may obtainRPAUID from the discoveree V2X UE and may provide container A and one ormore container B(s) matched for certain container C for that RPAUID tothat V2X UE. The V2X response code and V2X query filter may be expiredafter a certain amount of time.

In an example embodiment, in Model B the discoveree V2X UE may usecontainer A to response over interface PC5 to a received container Cwhich may be matched to the one or more container C(s). In an exampleembodiment, in Model B the container A and one or more container B whichmay be matched to a container C indicate discoveree UE's neighboringlist to the V2X group neighbors. In an example embodiment, in Model Bcontainer A and one or more container B which may be matched tocontainer C indicate one or more segment(s) of discoveree UE'sneighboring list to the V2X group neighbors.

In one example embodiment, container A may be V2X response code. In oneexample embodiment, container A may be V2X query filter. In one exampleembodiment, container A may be V2X query code.

In an example embodiment, in Model B the discoverer V2X UE may retrievethe PDUID and may provide it to the V2X application server. The V2Xapplication server may allocate RPAUID for PDUID which have beenprovided by that V2X UE. The discoverer V2X UE may use the obtainedRPAUID instead of PDUID. The V2X application server may store thebinding between the PDUID and RPAUID.

In an example embodiment, in Model B, the HPLMN V2X function obtainsRPAUID from the discoverer V2X UE and may provide V2X query code and theV2X response filter matched for a certain V2X response code for thatRPAUID to the discoverer V2X UE. The V2X query code and the V2X responsefilter may be expired after a certain amount of time.

In an example embodiment, in Model B, the HPLMN V2X function obtainsRPAUID from the discoverer V2X UE and may provide V2X query code and theV2X response filters matched for a certain V2X response code for thatRPAUID to the discoverer V2X UE. The V2X query code and the V2X responsefilters may be expired after a certain amount of time.

In an example embodiment, in Model B the discoverer V2X UE may use V2Xquery code to response over interface PC5 to find out it is matched tothe V2X response filter. In an example embodiment, in Model B thediscoverer V2X UE may use V2X query code to response over interface PC5to find out it is matched to one or more of the V2X response filters. Inan example embodiment, in Model B the V2X query code and one or more V2Xresponse filter(s) which may be matched to a V2X response code indicatediscoverer UE's neighboring list to the V2X group neighbors. In anexample embodiment, in Model B the V2X query code and one or more V2Xresponse filter(s) which may be matched to a V2X response code indicateone or more segment(s) of discoverer UE's neighboring list to the V2Xgroup neighbors.

In an example embodiment, in Model B the discoverer V2X UE may retrievethe PDUID and may provide it to the V2X application server. The V2Xapplication server may allocate RPAUID for PDUID which have beenprovided by that V2X UE. The discoverer V2X UE may use the obtainedRPAUID instead of PDUID. The V2X application server may store thebinding between the PDUID and RPAUID.

In an example embodiment, in Model B, the HPLMN V2X function may obtainRPAUID from the discoverer V2X UE and may provide container A and one ormore container B(s) matched for a certain container C for that RPAUID tothe discoverer V2X UE. The container A and the container B may beexpired after a certain amount of time.

In an example embodiment, in Model B the discoverer V2X UE may usecontainer A to response over interface PC5 to find out it is matched toone or more of container B(s). In an example embodiment, in Model B thecontainer A and one or more container B(s) which may be matched to acontainer C indicate discoverer UE's neighboring list to the V2X groupneighbors. In an example embodiment, in Model B container A and one ormore container B(s) which may be matched to a container C indicate oneor more segment(s) of discoverer UE's neighboring list to the V2X groupneighbors. In one example embodiment, container A may be V2X query code.In one example embodiment, container B may be V2X response filter. Inone example embodiment, container C may be V2X response code.

In one example embodiment, in the Model B, the V2X response filter ofthe discoverer V2X UE which may match V2X response code for the RPAUIDwhich may have been assigned to V2X discovery UE ID (PDUID) of thediscoveree V2X UE may comprise the vehicle type of the discoveree V2XUE. In one example embodiment, in the Model B, the V2X response filterof the discoverer V2X UE which may match V2X response code for theRPAUID which may have been assigned to V2X discovery UE ID (PDUID) ofthe discoveree V2X UE may comprise the pedestrian type of the discovereeV2X UE. In one example embodiment, in the Model B, the V2X responsefilter of the discoverer V2X UE which may match V2X response code forthe RPAUID which may have been assigned to V2X discovery UE ID (PDUID)of the discoveree V2X UE may comprise the infrastructure type of thediscoveree V2X UE. In one example embodiment, in the Model B, the V2Xresponse filter of the discoverer V2X UE which may match V2X responsecode for the RPAUID which may have been assigned to V2X discovery UE ID(PDUID) of the discoveree V2X UE may comprise the vehicle-to-vehicletype of the discoveree V2X UE. In one example embodiment, in the ModelB, the V2X response filter of the discoverer V2X UE which may match V2Xresponse code for the RPAUID which may have been assigned to V2Xdiscovery UE ID (PDUID) of the discoveree V2X UE may comprise thevehicle-to-pedestrian type of the discoveree V2X UE. In one exampleembodiment, in the Model B, the V2X response filter of the discovererV2X UE which may match V2X response code for the RPAUID which may havebeen assigned to V2X discovery UE ID (PDUID) of the discoveree V2X UEmay comprise the vehicle-to-infrastructure type of the discoveree V2XUE. In one example embodiment, in the Model B, the V2X response filterof the discoverer V2X UE which may match V2X response code for theRPAUID which may have been assigned to V2X discovery UE ID (PDUID) ofthe discoveree V2X UE may comprise the vehicle-to-network type of thediscoveree V2X UE.

In one example embodiment, in the Model B, the V2X response filter ofthe discoverer V2X UE which may match V2X response code for the RPAUIDwhich may have been assigned to V2X discovery UE ID (PDUID) of thediscoveree V2X UE may comprise at least two or more of the pedestriantype, the vehicle type, or the infrastructure type, vehicle-to-vehicletype, vehicle-to-pedestrian type, vehicle-to-network, and/orvehicle-to-infrastructure type of the discoveree V2X UE.

In one example embodiment, in the Model B, the V2X response filter ofthe discoverer V2X UE which may match V2X response code for the RPAUIDwhich may have been assigned to V2X discovery UE ID (PDUID) of thediscoveree V2X UE may comprise all of the pedestrian type, the vehicletype, the infrastructure type, vehicle-to-vehicle type,vehicle-to-pedestrian type, vehicle-to-network, andvehicle-to-infrastructure type of the discoveree V2X UE.

In one example embodiment, in the Model B, the V2X response filter ofthe discoverer V2X UE which may match V2X response code for the RPAUIDwhich may have been assigned to V2X discovery UE ID (PDUID) of thediscoveree V2X UE may comprise the emergency vehicle type of thediscoveree V2X UE. In one example embodiment, in the Model B, the V2Xresponse filter of the discoverer V2X UE which may match V2X responsecode for the RPAUID which may have been assigned to V2X discovery UE ID(PDUID) of the discoveree V2X UE may comprise the emergency pedestriantype of the discoveree V2X UE. In one example embodiment, in the ModelB, the V2X response filter of the discoverer V2X UE which may match V2Xresponse code for the RPAUID which may have been assigned to V2Xdiscovery UE ID (PDUID) of the discoveree V2X UE may comprise theemergency infrastructure type of the discoveree V2X UE. In one exampleembodiment, in the Model B, the V2X response filter of the discovererV2X UE which may match V2X response code for the RPAUID which may havebeen assigned to V2X discovery UE ID (PDUID) of the discoveree V2X UEmay comprise the emergency vehicle-to-vehicle type of the discoveree V2XUE. In one example embodiment, in the Model B, the V2X response filterof the discoverer V2X UE which may match V2X response code for theRPAUID which may have been assigned to V2X discovery UE ID (PDUID) ofthe discoveree V2X UE may comprise the emergency vehicle-to-pedestriantype of the discoveree V2X UE. In one example embodiment, in the ModelB, the V2X response filter of the discoverer V2X UE which may match V2Xresponse code for the RPAUID which may have been assigned to V2Xdiscovery UE ID (PDUID) of the discoveree V2X UE may comprise theemergency vehicle-to-infrastructure type of the discoveree V2X UE. Inone example embodiment, in the Model B, the V2X response filter of thediscoverer V2X UE which may match V2X response code for the RPAUID whichmay have been assigned to V2X discovery UE ID (PDUID) of the discovereeV2X UE may comprise the emergency vehicle-to-network type of thediscoveree V2X UE.

In one example embodiment, in the Model B, the V2X response filter ofthe discoverer V2X UE which may match V2X response code for the RPAUIDwhich may have been assigned to V2X discovery UE ID (PDUID) of thediscoveree V2X UE may comprise at least two or more of the emergencypedestrian type, the emergency vehicle type, or the emergencyinfrastructure type, emergency vehicle-to-vehicle type, emergencyvehicle-to-pedestrian type, emergency vehicle-to-network, and/oremergency vehicle-to-infrastructure type of the discoveree V2X UE.

In one example embodiment, in the Model B, the V2X response filter ofthe discoverer V2X UE which may match V2X response code for the RPAUIDwhich may have been assigned to V2X discovery UE ID (PDUID) of thediscoveree V2X UE may comprise all of the pedestrian type, the vehicletype, the infrastructure type, vehicle-to-vehicle type,vehicle-to-pedestrian type, vehicle-to-network, andvehicle-to-infrastructure type of the discoveree V2X UE.

In an example embodiment, shown in FIG. 46, the neighboring list of aV2X group member may be announced and may be broadcasted by using thepayload of user diagram protocol (UDP) with a set of informationelements comprising the neighboring list and the related informationelements for announcements.

In an example embodiment, an information element is shown in FIG. 47. Vmay be version number and may be set to 1. P may be set to 1 if there ispadding at the end of payload otherwise may be set to zero. A is addresstype which may be set to “0” if the V2X neighbor list announcer has aspecific type of address e.g. IPV4 address and may be set to “1” if ithas another specific type of address e.g. IPV6 address. C is compressedbit which may be set to “1” if the packet is compressed or may be set to“0” if otherwise. E is encryption bit which may be set to “1” if thepacket is encrypted or may be set to “0” if otherwise (if bothcompression and encryption are applied to the packet format, thecompression may need to be applied first). Packet Type (PT) may be toshow this is neighboring list (NL) and may be set to a certain value toindicate that this packet may contain the V2X neighboring list. Lengthmay be the length of the payload of the UDP packet.

In an example embodiment, real-time transport control protocol (RTCP)may be a sister protocol for real-time transport protocol (RTP) (with anexample in IETF RFC 3550). RTP may be used for transmission of mediabetween different entities while RTCP may be used for periodicallysending control information to maintain certain quality for the mediatransmission and also synchronization between the media streams. RTCPmay have been used as floor control signaling protocol for applicationsuch as push to talk over cellular (PoC) in OMA or mission criticalpush-to-talk (MCPTT) in 3GPP standard bodies. The protocol may be lightand may be transmitted over user datagram protocol (UDP) which isconnectionless and offers no guarantee to be delivered to the endpoint,but at the same time may not require any tedious connection orientedprocedures which may not be suitable for the wireless communications.Therefore, RTCP may be a good candidate for link layer transmission ofdata burst and thereby announcement of neighboring list.

RTCP packet format may be specified as following figure (as example isshown in IETF RFC 3550). FIG. 48 may show the format of RTCP for thetransportation of the neighboring list. V may be version number and maybe set to 2 (an example is shown in IETF RFC 3550). P may be set to 1 ifthere is padding at the end of payload otherwise may be set to zero. Ais address type which may be set to “0” if the V2X neighbor listannouncer has a specific type of address e.g. IPV4 address and may beset to “1” if it has another specific type of address e.g. IPV6 address.C is compressed bit which may be set to “1” if the packet is compressedor may be set to “0” if otherwise. E is encryption bit which may be setto “1” if the packet is encrypted or may be set to “0” if otherwise (ifboth compression and encryption are applied to the packet format, thecompression may need to be applied first). Packet Type (PT) may be toshow this is neighboring list (NL) and may be set to a certain value toindicate that this packet may contain the V2X neighboring list. Lengthmay be the length of the RTCP packet. SSRC may be the synchronizationsource identifier for the originator announcing the V2X NeighboringList. NLAP (4 Bytes) may be chosen to define the V2X neighboring listannouncement protocol packets to be unique with respect to otherapplication packets this V2X might receive; optional authenticationdata; and the list of the V2X neighbor ID and possible zero padding tomake this field a multiple of 32 bits.

The neighboring list announcement protocol (NLAP) may be broadcasted maybe broadcasted of a pre-defined channel with a pre-defined port number,an optional authentication data may be added so that the V2X users fromnon-affiliated groups may be able to ignore the neighboring listannouncements.

In an example embodiment, an information element in FIG. 46 and/or thepossible authentication data in FIG. 48 may be defined according to FIG.49, Authen ID field ID value may be a predefined binary value toindicate this field. Authen ID length ID with its binary value may showthe length of this field; and Authentication data may be theauthentication data to authenticate the announcer of the neighboringlist.

In one example embodiment, an information element in FIG. 46 and/or thepossible authentication data in FIG. 48 may be according to FIG. 50 (anexample is shown in IETF RFC 2974) with the format, where V is theversion number and may be set to “1”; P is the padding bit and may beset to “1” if authentication data may be padded to be a multiple of 32bits; Auth is authentication type which may be 4 bits and may be set to“0” if OpenPGP message format (an example in IETF RFC 2440) is employedfor authentication. It may be set to “1” if cryptographic message syntax(CMS) (an example in IETF RFC 3369 and IETF RFC 3370), is used forauthentication; and format specific authentication subheader may beaccording to one for OpenPGP authentication (an example in IETF RFC2440) or may be according to the one for CMS authentication (an examplein IETF RFC 3369 and IETF RFC 3370).

In one example embodiment, an information element in FIG. 46 and/or theneighbor ID field and possible zero padding to make this field amultiple of 32 bits in FIG. 48 may be according to FIG. 51, whereneighbor ID field ID may have a predefined binary value to indicate thisfield; neighbor ID length ID with its binary value may show the lengthof the field; number of Segments may be the total number of UDP packetsin FIG. 46 and/or RTCP packets in FIG. 48 which may be employed toallocate all the neighbors in the neighboring list; and segment numbermay be the current number of total segments used to announce all theneighbors in neighboring list.

The UDP packets in FIG. 46 and/or RTCP packet in FIG. 48 may begenerated periodically by the V2X group members. The periodicity may bepre-configured.

The example in FIG. 52 shows that the neighboring list are processedinto the UDP and/or RTCP packets comprising the neighboring listinformation. If the size of neighboring information is larger than thepayload of the UDP and/or RTCP packet, then neighboring list is dividedinto segments which individually gets processed by the UDP and/or RTCPpackets. The transmitting V2X UE transmits the UDP and/or RTCP packetson PC5 interface.

The example in FIG. 53 shows on the recipient side the recipient V2X UEsmay receive the UDP and/or RTCP packets with the neighboring listinformation which may be in segments. Having reverse processed the UDPand/or RTCP packets, the recipient V2X UE may parse the neighboring listor its segments from the reversed processed RTCP packets. If theneighboring list is in several segments, the recipient V2X UE collectall the segments from several received UDP and/or RTCP packets toreconstruct the entire neighboring list belonging to the transmittingV2X UE.

In one example embodiment, a V2X member may divide its neighbor listinto several segments. In one example embodiment, a V2X member maytransmit its neighboring list by use of a payload container. In oneexample embodiment, a V2X member may periodically transmit itsneighboring list by use of a payload container. In one exampleembodiment, a V2X member may transmit segments of its neighboring listby use of a payload container. In one example embodiment, a V2X membermay periodically transmit segments of its neighboring list by use of apayload container. In one example embodiment, the payload container maybe part of RTCP. In one example embodiment, the RTCP can be transmittedover UDP. In one example embodiment, the payload container may directlybe part of UDP. In one example embodiment, the encryption may be use toencrypt the information about V2X neighboring's neighboring list. In oneexample embodiment, the encryption may be use to encrypt the informationabout the segments V2X neighboring's neighboring list. In one exampleembodiment, the compression may be used to compress the informationabout the V2X members' neighboring list. In one example embodiment, theauthentication may be used to authenticate the V2X member announcing itsneighboring list. In one example embodiment, the payload containeridentifies the payload by an indicator. In one example embodiment, thepayload is identified by RTCP packet. In one example embodiment, a V2Xmember may receive a payload container comprising a V2X user'sneighboring list. In one example embodiment, a V2X member may receive apayload container comprising a segment of a V2X user's neighboring list.In one example embodiment, a recipient V2X member collects all thesegments of the neighboring list's segments to build the neighboringlist of the announcing V2X member.

In one example embodiment, a V2X member may receive the payloadcontainer as a part of a UDP packet. In one example embodiment, a V2Xmember may receive the payload container as a part of an RTCP packet. Inone example embodiment, a V2X member may receive the RTCP packet overUDP. In one example embodiment, the received neighboring list may beencrypted. In one example embodiment, the received segment of theneighboring list may be encrypted. In one example embodiment, thereceived neighboring list may be compressed. In one example embodiment,the received segment of the neighboring list may be compressed. In oneexample embodiment, the recipient V2X member may need to authenticatethe V2X member who announces its neighboring list. In one exampleembodiment, the recipient V2X member may need to authenticate the V2Xmember who announces segments of its neighboring list. In one exampleembodiment, the recipient V2X member may receive the modified neighborlist and may replace the current local one with the received one. In oneexample embodiment, the recipient V2X member may receive the sameneighbor list and may replace the current local one with the receivedone. In one example embodiment, the recipient V2X member may receive themodified segment of the neighbor list and may replace the current localone with the received one. In one example embodiment, the recipient V2Xmember may receive the same segment neighbor list and may replace thecurrent local one with the received one. In one example embodiment, therecipient V2X member may need to collect all the received segments fromthe announcing V2X member to create the announcing V2X user'sneighboring list.

According to various embodiments, a device such as, for example, awireless device, off-network wireless device, a V2X wireless device, abase station, a V2X network entity, an IMS network entity, and/or thelike, may comprise one or more processors and memory. The memory maystore instructions that, when executed by the one or more processors,cause the device to perform a series of actions. Embodiments of exampleactions are illustrated in the accompanying figures and specification.Features from various embodiments may be combined to create yet furtherembodiments.

FIG. 54 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 5410, a first V2X wireless device maytransmit a first discovery request to a V2X network entity. The V2Xnetwork entity may comprise a first wireless device identifier and a V2Xvalue. The V2X value may indicate a V2X communication capability. At5420, the first V2X wireless device may receive a first discoveryresponse from the V2X network entity. The first discovery response maycomprise a first discovery code. The first discovery code may correspondto at least the V2X value. At 5430, the first V2X wireless device mayperform a discovery procedure. The discovery procedure may employ thefirst discovery code. At 5440, the first V2X wireless device maycommunicate, with a second V2X wireless device by employing the V2Xcommunication capability, one or more packets in response to thediscovery procedure connecting the first V2X wireless device with thesecond V2X wireless device.

According to an embodiment, the discovery procedure may receive a seconddiscovery code from the second V2X wireless device. The discoveryprocedure may further determine the type of V2X communication of thesecond V2X wireless device from the second discovery code. According toan embodiment, the first discovery code may correspond to at least thefirst V2X wireless device identifier. According to an embodiment, thecommunication, by the first V2X wireless device with the second V2Xwireless device, may employ a type of V2X communication compatible withthe V2X communication capability. According to an embodiment, thediscovery procedure broadcast, by the first V2X wireless device, thefirst discovery code. The first discovery code may be configured toindicate the type of V2X communication of the first V2X wireless devicewith the second V2X wireless device after the first wireless device isdiscovered by the second V2X wireless device. According to anembodiment, the discovery procedure may receive, by the first V2Xwireless device from the second V2X wireless device, a second discoverycode. The first V2X wireless device may determine the type of V2Xcommunication of the second V2X wireless device from the seconddiscovery code.

According to an embodiment, the first discovery code may correspond toat least the first V2X wireless device identifier. According to anembodiment, the first discovery code indicates the type of V2Xcommunication over a PC5 reference point. According to an embodiment,the first discovery code indicates the type of V2X communication over aPC5 reference point via a third V2X wireless device. According to anembodiment, the first discovery code indicates the type of V2Xcommunication to the V2X network entity via a V2X wireless device byemploying a PC5 reference point.

According to an embodiment, the first discovery code indicates at leastone of: a vehicle-to-vehicle application; a vehicle-to-pedestrianapplication; a vehicle-to-infrastructure application; avehicle-to-network application; an emergency vehicle-to-vehicleapplication; an emergency vehicle-to-pedestrian application; anemergency vehicle-to-infrastructure application; and an emergencyvehicle-to-network application.

According to an embodiment, the discovery procedure further comprisesdetecting, by the second V2X wireless device, the first V2X wirelessdevice. The discovery procedure may determine, by the second V2Xwireless device, the type of V2X communication of the first V2X wirelessdevice from the first discovery code. According to an embodiment, thediscovery procedure may respond, by the second V2X wireless device tothe first V2X wireless device, the second discovery code. The discoveryprocedure may determine, by the first V2X wireless device, the type ofV2X communication of the second V2X wireless device from the seconddiscovery code.

According to an embodiment, the second discovery code may indicate thetype of V2X communication over a PC5 reference point. According to anembodiment, the second discovery code may indicate the type of V2Xcommunication over a PC5 reference point via a third V2X wirelessdevice. According to an embodiment, the second discovery code mayindicate the type of V2X communication to the V2X network entity via aV2X wireless device by employing the PC5 reference point. According toan embodiment, the second discovery code may indicate at least one of: avehicle-to-vehicle application; a vehicle-to-pedestrian application; avehicle-to-infrastructure application; a vehicle-to-network application;an emergency vehicle-to-vehicle application; an emergencyvehicle-to-pedestrian application; an emergencyvehicle-to-infrastructure application; and an emergencyvehicle-to-network application.

FIG. 55 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 5510, a wireless device may transmit asession initiation protocol (SIP) REGISTER request to an internetprotocol multimedia subsystem (IMS) network entity. The SIP REGISTERRequest may comprise a first SIP header field. The first SIP headerfield may comprise one or more indicators for V2X capabilities of thewireless device. At 5520, the wireless device may receive a SIP responsefrom the IMS network entity. The SIP response may comprise the first SIPheader field confirming the registration of the V2X capabilities. At5530, the wireless device may receive a second SIP request from the IMSnetwork entity. The second SIP request may comprise a second SIP headerfield. The second SIP header field may comprise one or more indicatorsfor V2X multicast service capabilities. The second SIP request maycomprise one or more configuration parameters to receive packets via V2Xbroadcast and multicast bearers. At 5540, the wireless device maytransmit a second SIP response to the IMS network entity. At 5550, thewireless device may receive packets via the V2X broadcast and multicastbearers. According to an embodiment, the SIP header field may comprise aSIP Contact header field.

According to an embodiment, the one or more indicators for V2X multicastservice capabilities may comprise at least one of: an IMS communicationservice identifier (ICSI); and an IMS application reference identifier(IARI). According to an embodiment, the one or more indicators for V2Xcapabilities comprise at least one of: an IMS communication serviceidentifier (ICSI); and an IMS application reference identifier (IARI).

According to an embodiment, the V2X capabilities comprise PC5communications V2X capabilities of the first wireless device. Accordingto an embodiment, the V2X capabilities comprise at least one of: avehicle to pedestrian capability; a vehicle to infrastructurecapability; a vehicle to vehicle capability; a vehicle to networkcapability, a combination thereof, and/or the like. According to anembodiment, the V2X capabilities indicate an emergency communicationcapability. According to an embodiment, the V2X capabilities may havedifferent priorities.

According to an embodiment, the IMS network entity may maintaininformation about the V2X capabilities of the wireless device. Accordingto an embodiment, the IMS network entity may employs the V2Xcapabilities of the wireless device to forward a SIP request towards thewireless device.

FIG. 56 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 5610, a second wireless device may receive afirst session initiation protocol (SIP) REGISTER request from a firstwireless device. The first session initiation protocol (SIP) REGISTERrequest may comprise a SIP header field. The SIP header field maycomprise one or more indicators for V2X capabilities of the firstwireless device. At 5620, the second wireless device may transmit asecond SIP REGISTER request to an IMS network entity. The second SIPREGISTER request may comprise the SIP header field. At 5630, the secondwireless device may receive a second SIP response from the IMS networkentity. The second SIP response may comprise the SIP header field. At5640, the second wireless device may transmit a first SIP response tothe first wireless device. The first SIP response may comprise the SIPheader field. At 5650, the first wireless device may determine, from thefirst SIP response comprising the SIP header field, registration of theV2X capabilities of the first wireless device with the IMS networkentity.

FIG. 57 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 5710, a wireless device may transmit a firstsession initiation protocol (SIP) request to an internet protocolmultimedia subsystem (IMS) network entity. The first SIP request maycomprise at least: a SIP header field which comprises one or moreindicators for V2X multicast service capabilities, and an indicator forloss of packets via V2X broadcast and multicast bearer. At 5720, thewireless device may receive a response from the IMS network entity. Theresponse may comprise a first confirmation for the first SIP request. At5730, the wireless device may receive a second SIP request from the IMSnetwork entity. The second SIP request may comprise a second SIP headerfield. The second SIP header field may comprise the one or moreindicators for V2X multicast service capabilities, and one or moreconfiguration parameters to receive the packets via V2X broadcast andmulticast bearers. At 5740, the wireless device may transmit a secondSIP response to the IMS network entity. The second SIP response maycomprise a second confirmation for the second SIP request. At 5750, thewireless device may receive the packets via the V2X broadcast andmulticast bearers.

FIG. 58 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 5810, a wireless device may receive, by asecond wireless device from a first wireless device, a first sessioninitiation protocol (SIP) request. The first SIP request may comprise atleast: a SIP header field which comprises one or more indicators for V2Xmulticast service capabilities, and indicator of loss of packets via V2Xbroadcast and multicast bearer. At 5820, the second wireless device maytransmit a second SIP request to an internet protocol multimediasubsystem (IMS) network entity. The second SIP request may comprise theSIP header field and the indicator for the loss of packets via V2Xbroadcast and multicast bearer. At 5830, the second wireless device mayreceive a third SIP request from the IMS network entity. The third SIPrequest may comprise the SIP header field which comprises the one ormore indicators for V2X multicast service capabilities, and one or moreconfiguration parameters to receive the packets via V2X broadcast andmulticast bearers. At 5840 the second wireless device may transmit afourth SIP request to the first wireless device. The fourth SIP requestmay comprise the SIP header field and one or more configurationparameters to receive the packets via V2X broadcast and multicastbearers. At 5850, the first wireless device may receive via the secondwireless device, the packets via V2X broadcast and multicast bearers.

In this specification, “a” and “an” and similar phrases are to beinterpreted as “at least one” and “one or more.” In this specification,the term “may” is to be interpreted as “may, for example.” In otherwords, the term “may” is indicative that the phrase following the term“may” is an example of one of a multitude of suitable possibilities thatmay, or may not, be employed to one or more of the various embodiments.If A and B are sets and every element of A is also an element of B, A iscalled a subset of B. In this specification, only non-empty sets andsubsets are considered. For example, possible subsets of B={cell1,cell2} are: {cell1}, {cell2}, and {cell1, cell2}.

In this specification, various embodiments are disclosed. Limitations,features, and/or elements from the disclosed example embodiments may becombined to create further embodiments within the scope of thedisclosure.

In this specification, parameters (Information elements: IEs) maycomprise one or more objects, and each of those objects may comprise oneor more other objects. For example, if parameter (IE) N comprisesparameter (IE) M, and parameter (IE) M comprises parameter (IE) K, andparameter (IE) K comprises parameter (information element) J, then, forexample, N comprises K, and N comprises J. In an example embodiment,when one or more messages comprise a plurality of parameters, it impliesthat a parameter in the plurality of parameters is in at least one ofthe one or more messages, but does not have to be in each of the one ormore messages.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an isolatableelement that performs a defined function and has a defined interface toother elements. The modules described in this disclosure may beimplemented in hardware, software in combination with hardware,firmware, wetware (i.e., hardware with a biological element) or acombination thereof, all of which are behaviorally equivalent. Forexample, modules may be implemented as a software routine written in acomputer language configured to be executed by a hardware machine (suchas C, C++, Fortran, Java, Basic, Matlab or the like) or amodeling/simulation program such as Simulink, Stateflow, GNU Octave, orLabVIEWMathScript. Additionally, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers and microprocessors are programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDsare often programmed using hardware description languages (HDL) such asVHSIC hardware description language (VHDL) or Verilog that configureconnections between internal hardware modules with lesser functionalityon a programmable device. Finally, it needs to be emphasized that theabove-mentioned technologies are often used in combination to achievethe result of a functional module.

The disclosure of this patent document incorporates material which issubject to copyright protection. The copyright owner has no objection tothe facsimile reproduction by anyone of the patent document or thepatent disclosure, as it appears in the Patent and Trademark Officepatent file or records, for the limited purposes required by law, butotherwise reserves all copyright rights whatsoever.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example, and notlimitation. It will be apparent to persons skilled in the relevantart(s) that various changes in form and detail can be made thereinwithout departing from the spirit and scope. In fact, after reading theabove description, it will be apparent to one skilled in the relevantart(s) how to implement alternative embodiments. Thus, the presentembodiments should not be limited by any of the above describedexemplary embodiments. In particular, it should be noted that, forexample purposes, the above explanation has focused on the example(s)using FDD communication systems. However, one skilled in the art willrecognize that embodiments of the invention may also be implemented in asystem comprising one or more TDD cells (e.g. frame structure 2 and/orframe structure 3-licensed assisted access). The disclosed methods andsystems may be implemented in wireless or wireline systems. The featuresof various embodiments presented in this invention may be combined. Oneor many features (method or system) of one embodiment may be implementedin other embodiments. Only a limited number of example combinations areshown to indicate to one skilled in the art the possibility of featuresthat may be combined in various embodiments to create enhancedtransmission and reception systems and methods.

In addition, it should be understood that any figures which highlightthe functionality and advantages, are presented for example purposesonly. The disclosed architecture is sufficiently flexible andconfigurable, such that it may be utilized in ways other than thatshown. For example, the actions listed in any flowchart may bere-ordered or only optionally used in some embodiments.

Further, the purpose of the Abstract of the Disclosure is to enable theU.S. Patent and Trademark Office and the public generally, andespecially the scientists, engineers and practitioners in the art whoare not familiar with patent or legal terms or phraseology, to determinequickly from a cursory inspection the nature and essence of thetechnical disclosure of the application. The Abstract of the Disclosureis not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include theexpress language “means for” or “step for” be interpreted under 35U.S.C. 112(f). Claims that do not expressly include the phrase “meansfor” or “step for” are not to be interpreted under 35 U.S.C. 112.

1. A method comprising: receiving, by a first wireless device from abase station of a cellular network, a message comprising an indicationof a vehicle-to-everything (V2X) group; determining, by the firstwireless device, that a second wireless device is associated with theV2X group; determining, by the first wireless device, an updated list,of neighboring V2X group members of the first wireless device, thatincludes the second wireless device; and sending, by the first wirelessdevice to a third wireless device, the updated list.
 2. The method ofclaim 1, wherein the indication comprises a V2X application identifier.3. The method of claim 1, wherein the updated list comprises at leastone V2X group member that is within a communication range of the firstwireless device.
 4. The method of claim 1, wherein the determining thatthe second wireless device is associated with the V2X group comprisesreceiving at least one discovery message received from the secondwireless device.
 5. The method of claim 1, wherein the sending theupdated list comprises periodically sending, by the first wirelessdevice, a V2X discovery message comprising the updated list.
 6. Themethod of claim 1, wherein the sending the updated list comprisessending the updated list via a PC5 interface.
 7. The method of claim 1,further comprising receiving, by the first wireless device from thesecond wireless device, a list of neighboring V2X group members of thesecond wireless device, wherein the determining the updated list thatincludes the second wireless device is based on a determination that thelist of neighboring V2X group members of the second wireless device isdifferent from a previous list of neighboring V2X group members of thefirst wireless device.
 8. A first wireless device comprising: one ormore processors; and memory storing instructions that, when executed bythe one or more processors, cause the first wireless device to: receive,from a base station of a cellular network, a message comprising anindication of a vehicle-to-everything (V2X) group; determine that asecond wireless device is associated with the V2X group; determine anupdated list, of neighboring V2X group members of the first wirelessdevice, that includes the second wireless device; and send, to a thirdwireless device, the updated list.
 9. The first wireless device of claim8, wherein the indication comprises a V2X application identifier. 10.The first wireless device of claim 8, wherein the updated list comprisesat least one V2X group member that is within a communication range ofthe first wireless device.
 11. The first wireless device of claim 8,wherein the instructions, when executed by the one or more processors,cause the first wireless device to determine that the second wirelessdevice is associated with the V2X group by receiving, from the secondwireless device, at least one discovery message.
 12. The first wirelessdevice of claim 8, wherein the instructions, when executed by the one ormore processors, cause the first wireless device to send the updatedlist by periodically sending a V2X discovery message comprising theupdated list.
 13. The first wireless device of claim 8, wherein theinstructions, when executed by the one or more processors, cause thefirst wireless device to send the updated list by sending the updatedlist via a PC5 interface.
 14. The first wireless device of claim 8,wherein the instructions, when executed by the one or more processors,further cause the first wireless device to receive, from the secondwireless device, a list of neighboring V2X group members of the secondwireless device, and wherein the instructions, when executed by the oneor more processors, cause the first wireless device to determine theupdated list that includes the second wireless device based on adetermination that the list of neighboring V2X group members of thesecond wireless device is different from a previous list of neighboringV2X group members of the first wireless device.
 15. A non-transitorycomputer-readable medium storing instructions that, when executed,configure a first wireless device to: receive, from a base station of acellular network, a message comprising an indication of avehicle-to-everything (V2X) group; determine that a second wirelessdevice is associated with the V2X group; determine an updated list, ofneighboring V2X group members of the first wireless device, thatincludes the second wireless device; and send, to a third wirelessdevice, the updated list.
 16. The non-transitory computer-readablemedium of claim 15, wherein the indication comprises a V2X applicationidentifier.
 17. The non-transitory computer-readable medium of claim 15,wherein the updated list comprises at least one V2X group member that iswithin a communication range of the first wireless device.
 18. Thenon-transitory computer-readable medium of claim 15, wherein theinstructions, when executed, cause the first wireless device todetermine that the second wireless device is associated with the V2Xgroup by receiving, from the second wireless device, at least onediscovery message.
 19. The non-transitory computer-readable medium ofclaim 15, wherein the instructions, when executed, cause the firstwireless device to send the updated list by periodically sending a V2Xdiscovery message comprising the updated list.
 20. The non-transitorycomputer-readable medium of claim 15, wherein the instructions, whenexecuted, cause the first wireless device to send the updated list bysending the updated list via a PC5 interface.
 21. The non-transitorycomputer-readable medium of claim 15, wherein the instructions, whenexecuted, further cause the first wireless device to receive, from thesecond wireless device, a list of neighboring V2X group members of thesecond wireless device, and wherein the instructions, when executed,cause the first wireless device to determine the updated list thatincludes the second wireless device based on a determination that thelist of neighboring V2X group members of the second wireless device isdifferent from a previous list of neighboring V2X group members of thefirst wireless device.
 22. A system comprising: a base station of acellular network; and a first wireless device, wherein the base stationis configured to: send, to the first wireless device, a messagecomprising an indication of a vehicle-to-everything (V2X) group, whereinthe first wireless device is configured to: determine that a secondwireless device is associated with the V2X group; determine an updatedlist, of neighboring V2X group members of the first wireless device,that includes the second wireless device; and send, to a third wirelessdevice, the updated list.
 23. The system of claim 22, wherein theindication comprises a V2X application identifier.
 24. The system ofclaim 22, wherein the updated list comprises at least one V2X groupmember that is within a communication range of the first wirelessdevice.
 25. The system of claim 22, wherein the first wireless device isconfigured to determine that the second wireless device is associatedwith the V2X group by receiving, from the second wireless device, atleast one discovery message.
 26. The system of claim 22, wherein thefirst wireless device is configured to send the updated list byperiodically sending a V2X discovery message comprising the updatedlist.
 27. The system of claim 22, wherein the first wireless device isconfigured to send the updated list by sending the updated list via aPC5 interface.
 28. The system of claim 22, wherein the first wirelessdevice is further configured to receive, from the second wirelessdevice, a list of neighboring V2X group members of the second wirelessdevice, and wherein the first wireless device is configured to determinethe updated list that includes the second wireless device based on adetermination that the list of neighboring V2X group members of thesecond wireless device is different from a previous list of neighboringV2X group members of the first wireless device.